Skip to content

Commit d08b6a6

Browse files
authored
Merge pull request #83 from actions/2.0.2-release
Bump version to 2.0.2
2 parents 181154c + 4bebd21 commit d08b6a6

File tree

3 files changed

+43
-3
lines changed

3 files changed

+43
-3
lines changed

CONTRIBUTING.md

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,46 @@ Here are a few things you can do that will increase the likelihood of your pull
2828
- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
2929
- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
3030

31+
## Cutting a new release
32+
33+
<details>
34+
35+
_Note: these instructions are for maintainers_
36+
37+
1. Update the version number in [package.json](https://github.com/actions/go-dependency-submission/blob/main/package.json) and run `npm i` to update the lockfile.
38+
1. Go to [Draft a new
39+
release](https://github.com/actions/go-dependency-submission/releases/new)
40+
in the Releases page.
41+
1. Make sure that the `Publish this Action to the GitHub Marketplace`
42+
checkbox is enabled
43+
44+
<img width="481" alt="Screenshot 2022-06-15 at 12 08 19" src="https://user-images.githubusercontent.com/2161/173822484-4b60d8b4-c674-4bff-b5ff-b0c4a3650ab7.png">
45+
46+
3. Click "Choose a tag" and then "Create new tag", where the tag name
47+
will be your version prefixed by a `v` (e.g. `v1.2.3`).
48+
4. Use a version number for the release title (e.g. "1.2.3").
49+
50+
<img width="700" alt="Screenshot 2022-06-15 at 12 08 36" src="https://user-images.githubusercontent.com/2161/173822548-33ab3432-d679-4dc1-adf8-b50fdaf47de3.png">
51+
52+
5. Add your release notes. If this is a major version make sure to
53+
include a small description of the biggest changes in the new version.
54+
6. Click "Publish Release".
55+
56+
You now have a tag and release using the semver version you used
57+
above. The last remaining thing to do is to move the dynamic version
58+
identifier to match the current SHA. This allows users to adopt a
59+
major version number (e.g. `v1`) in their workflows while
60+
automatically getting all the
61+
minor/patch updates.
62+
63+
To do this just checkout `main`, force-create a new annotated tag, and push it:
64+
65+
```
66+
git tag -fa v2 -m "Updating v2 to 2.0.1"
67+
git push origin v2 --force
68+
```
69+
</details>
70+
3171
## Resources
3272

3373
- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)

package-lock.json

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "go-dependency-submission",
3-
"version": "2.0.1",
3+
"version": "2.0.2",
44
"description": "Go Dependency Submission",
55
"main": "dist/index.js",
66
"scripts": {

0 commit comments

Comments
 (0)