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.

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

Release: 0.2.0 #109

Merged
merged 6 commits into from
Aug 30, 2023
Merged

Release: 0.2.0 #109

merged 6 commits into from
Aug 30, 2023

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Aug 29, 2023

  • Branch: Starting from develop, cut a release branch named release/0.2.0 for your changes.
  • Version bump: Bump the version number in package.json and package-lock.json if it does not already reflect the version being released.
  • Changelog: Add/update the changelog in CHANGELOG.md.
  • Props: Update CREDITS.md file with any new contributors, confirm maintainers are accurate.
  • Readme updates: Make any other readme changes as necessary in README.md.
  • Merge: Make a non-fast-forward merge from your release branch to develop (or merge the Pull Request), then merge develop into trunk (git checkout develop && git pull origin develop && git checkout trunk && git pull origin trunk && git merge --no-ff develop). trunk contains the stable development version.
  • Push: Push your trunk branch to GitHub (e.g. git push origin trunk).
  • Release: Create a new release, naming the tag and the release with the new version number, and targeting the trunk branch. Paste the changelog from CHANGELOG.md into the body of the release and include a link to the closed issues on the milestone. The release should now appear under releases.
  • Close milestone: Edit the milestone with release date (in the Due date (optional) field) and link to GitHub release (in the Description field), then close the milestone.
  • Punt incomplete items: If any open issues or PRs which were milestoned for 0.2.0 do not make it into the release, update their milestone to 0.3.0 or Future Release.

@github-actions github-actions bot requested a review from a team as a code owner August 29, 2023 21:18
@github-actions github-actions bot requested review from Sidsector9 and removed request for a team August 29, 2023 21:18
@dkotter dkotter removed the request for review from Sidsector9 August 29, 2023 21:20
@dkotter dkotter self-assigned this Aug 29, 2023
@dkotter dkotter added this to the 0.2.0 milestone Aug 29, 2023
@dkotter dkotter requested a review from jeffpaul as a code owner August 29, 2023 21:45
jeffpaul
jeffpaul previously approved these changes Aug 29, 2023
Copy link
Member

@jeffpaul jeffpaul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks for handling the release!

@dkotter dkotter merged commit 8101b6c into develop Aug 30, 2023
@dkotter dkotter deleted the release/0.2.0 branch August 30, 2023 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants