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 version 2.1.3 #127

Closed
11 tasks done
dkotter opened this issue Nov 15, 2024 · 0 comments · Fixed by #128
Closed
11 tasks done

Release version 2.1.3 #127

dkotter opened this issue Nov 15, 2024 · 0 comments · Fixed by #128
Assignees
Milestone

Comments

@dkotter
Copy link
Collaborator

dkotter commented Nov 15, 2024

This issue is for tracking changes for the 2.1.3 release. Target release date: November 2024.

Release instructions

  • Branch: Starting from develop, cut a release branch named release/2.1.3 for your changes.
  • Version bump: Bump the version number in package.json, package-lock.json and any other relevant files 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.
  • New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .gitattributes.
  • Readme updates: Make any other readme changes as necessary.
  • Merge: Make a non-fast-forward merge from your release branch to develop (or merge the pull request), then do the same for develop into trunk (git checkout 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.
  • 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 2.1.3 do not make it into the release, update their milestone to 2.2.0 or Future Release.
@dkotter dkotter added the type:enhancement New feature or request. label Nov 15, 2024
@dkotter dkotter self-assigned this Nov 15, 2024
@dkotter dkotter removed the type:enhancement New feature or request. label Nov 15, 2024
@dkotter dkotter added this to the 2.1.3 milestone Nov 15, 2024
@dkotter dkotter mentioned this issue Nov 15, 2024
4 tasks
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 a pull request may close this issue.

1 participant