Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Show latest version number instead of "upcoming" in changelog #1223

Merged
merged 1 commit into from Nov 4, 2014
Merged

Show latest version number instead of "upcoming" in changelog #1223

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 5 additions & 0 deletions release.sh
View file
Open in desktop
Expand Up @@ -21,6 +21,11 @@ github-changes -o request -r request \
--only-pulls --use-commit-body \
|| exit 1

# Since the tag for the new version hasn't been pushed yet, any changes in it
# will be marked as "upcoming"
version="$(grep '"version"' package.json | cut -d'"' -f4)"
sed -i -e "s/^### upcoming/### v$version/" CHANGELOG.md

# This may fail if no changelog updates
# TODO: would this ever actually happen? handle it better?
git add CHANGELOG.md; git commit -m 'Update changelog'
Expand Down