8000 Bump version metadata to produce correct tester and nightly build precedence by per1234 · Pull Request #1492 · arduino/arduino-ide · GitHub
[go: up one dir, main page]
Skip to content

Bump version metadata to produce correct tester an 8000 d nightly build precedence #1492

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

Merged
merged 5 commits into from
Sep 26, 2022
Merged

Bump version metadata to produce correct tester and nightly build precedence #1492

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
c08cf3d
Move package metadata update step to dedicated section of release docs
per1234 Sep 24, 2022
6833c91
Format release procedure document as ordered list
per1234 Sep 25, 2022
751114a
Adjust release procedure to produce correct tester and nightly build …
per1234 Sep 25, 2022
34ac727
Bump version metadata to produce correct tester and nightly build pre…
per1234 Sep 25, 2022
4333841
Correct issue report guide link in issue template chooser
per1234 Sep 25, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Move package metadata update step to dedicated section of release docs 
Previously the instructions for updating the npm package metadata, submitting a PR for that, and merging the PR was in
the same section as the tag push instructions in the release procedure documentation.

These two operations are distinct from each other. Mashing them into a single step makes the release procedure document
difficult to read and the process more prone to error.

For this reason, a dedicated step is used for each of the two things.
  • Loading branch information
@per1234
per1234 committed Sep 24, 2022
commit c08cf3d97e8a647cc8505b52d4a2a565567c7d41
6 changes: 4 additions & 2 deletions docs/internal/release-procedure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,9 @@ It will be shown in these search results:

https://github.com/arduino/arduino-ide/pulls/app%2Fgithub-actions

## ⚙ Create the release on GitHub
## ⚙ Update metadata of packages

First of all, you need to **set the new version in all the `package.json` files** across the app (`./package.json`, `./arduino-ide-extension/package.json`, and `./electron-app/package.json`), create a PR, and merge it on the `main` branch.
You need to **set the new version in all the `package.json` files** across the app (`./package.json`, `./arduino-ide-extension/package.json`, and `./electron-app/package.json`), create a PR, and merge it on the `main` branch.

To do so, you can make use of the `update:version` script.

Expand All @@ -29,6 +29,8 @@ git push origin version-<YOUR_VERSION>

replacing `<YOUR_VERSION>` with the version you want to release. Then create a PR and merge it.

## 🚢 Create the release on GitHub

Then, you need to **create and push the new tag** and wait for the release to appear on [the "**Releases**" page](https://github.com/arduino/arduino-ide/releases).

⚠ Doing this will create a new release and users who already have the IDE installed will be notified from the automatic updater that a new version is available. Do not push the tag if you don't want that.
Expand Down
0