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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release version 1.0.0 #67

Closed
19 tasks done
jeffpaul opened this issue Mar 22, 2022 · 3 comments 路 Fixed by #68
Closed
19 tasks done

Release version 1.0.0 #67

jeffpaul opened this issue Mar 22, 2022 · 3 comments 路 Fixed by #68
Assignees
@cadic @jeffpaul
Milestone
1.0.0

Comments

@jeffpaul
Copy link
Member

jeffpaul commented Mar 22, 2022 •
edited by cadic
Loading

Describe your question

This issue is for tracking changes for the 1.0.0 release. 馃帀 Target release date: April 2022.

Pre-release steps

Release steps

  • Branch: Starting from develop, cut a release branch named release/1.0.0 for your changes.
  • Version bump: Bump the version number in wpcli-vulnerability-scanner.php if it does not already reflect the version being released.
  • Changelog: Add/update the changelog in CHANGELOG.md.
  • Props: update CREDITS.md 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 .distignore.
  • 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 latest stable release.
  • 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 the 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 1.0.0 do not make it into the release, update their milestone to 1.1.0, or Future Release.

Post-release steps

  • Ensure release publishes to npm
  • Investigate automation in publishing future releases to npm

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jeffpaul jeffpaul added this to the 1.0.0 milestone Mar 22, 2022
@jeffpaul jeffpaul self-assigned this Mar 22, 2022
@cadic cadic self-assigned this Mar 24, 2022
@cadic cadic mentioned this issue Mar 24, 2022
Merged
6 tasks
@jeffpaul jeffpaul reopened this Apr 12, 2022
@jeffpaul
Copy link
Member Author

Reopened for @cadic to work on the final steps in the release process

@cadic
Copy link
Contributor

cadic commented Apr 13, 2022

@jeffpaul the remaining steps are complete

@cadic cadic closed this as completed Apr 13, 2022
@cadic
Copy link
Contributor

cadic commented Apr 13, 2022

@jeffpaul FYI, the release was pushed to https://packagist.org/packages/10up/wpcli-vulnerability-scanner#1.0.0 automatically

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cadic cadic

@jeffpaul jeffpaul

Labels
None yet
Projects
None yet
Milestone
1.0.0
Development

Successfully merging a pull request may close this issue.

Release/1.0.0 10up/wpcli-vulnerability-scanner
2 participants
@cadic @jeffpaul