Skip to content

fix: minor fixes related to release #5732

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

Merged
merged 5 commits into from
Nov 1, 2022
Merged

Conversation

jsjoeio
Copy link
Contributor

@jsjoeio jsjoeio commented Oct 28, 2022

Description

This makes some minor changes to progress us towards a smoother release.

Testing Plan

  1. try on my fork of code-server (see build here: https://github.com/jsjoeio/code-server/actions/runs/3348696732/jobs/5548022068)
  2. run draft-release: double-check npm-package is in release assets (successful download/upload)
  3. publish release
  4. ensure that the npm job successfully downloaded the right asset: https://github.com/jsjoeio/code-server/actions/runs/3364354246/jobs/5578605147

Fixes #5148

This removes the need to update this version with every version change.
@jsjoeio jsjoeio changed the title fix: use * for test plugin engines fix: minor fixes related to release Oct 28, 2022
@jsjoeio jsjoeio self-assigned this Oct 28, 2022
@jsjoeio jsjoeio temporarily deployed to npm October 28, 2022 20:12 Inactive
@github-actions
Copy link

github-actions bot commented Oct 28, 2022

✨ code-server dev build published to npm for PR #5732!

  • Last publish status: success
  • Commit: bb0251a

To install in a local project, run:

npm install @coder/code-server-pr@5732

To install globally, run:

npm install -g @coder/code-server-pr@5732

@codecov
Copy link

codecov bot commented Oct 28, 2022

Codecov Report

Merging #5732 (bb0251a) into main (ee47293) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #5732   +/-   ##
=======================================
  Coverage   72.65%   72.65%           
=======================================
  Files          30       30           
  Lines        1682     1682           
  Branches      369      369           
=======================================
  Hits         1222     1222           
  Misses        397      397           
  Partials       63       63           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ee47293...bb0251a. Read the comment docs.

This adds a new job to `release.yaml` to upload the `npm-package` to the
release assets which will also allow us to download it in the
`publish.yaml` workflow.
@github-actions
Copy link

github-actions bot commented Oct 28, 2022

✨ code-server docs for PR #5732 is ready! It will be updated on every commit.

@jsjoeio jsjoeio temporarily deployed to npm October 28, 2022 20:28 Inactive
@jsjoeio jsjoeio temporarily deployed to npm October 28, 2022 22:16 Inactive
@jsjoeio
Copy link
Contributor Author

jsjoeio commented Oct 28, 2022

Couldn't get the download part working right away. Will need to keep testing. See here: https://github.com/jsjoeio/code-server/actions/runs/3348950456/jobs/5548526826

@jsjoeio jsjoeio marked this pull request as ready for review October 31, 2022 20:02
@jsjoeio jsjoeio requested a review from a team as a code owner October 31, 2022 20:02
@jsjoeio jsjoeio temporarily deployed to npm October 31, 2022 20:04 Inactive
@@ -141,8 +141,7 @@ changelog](https://github.com/emacs-mirror/emacs/blob/master/etc/NEWS).

### Publishing a release

1. Create a new branch called `release/v0.0.0` (replace 0s with actual version aka v4.5.0)
1. If you don't do this, the `npm-brew` GitHub workflow will fail. It looks for the release artifacts under the branch pattern.
1. Create a new branch called `release`
Copy link
Member

Choose a reason for hiding this comment

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

I wonder if we should still call this release/v{version} because it is more descriptive of the changeset. Plus it could get weird if we ever need to backport or release multiple versions at once and if you have an old release branch checked out you would have to force reset which could seem weird because you might think "I have never checked out this release before" but because the name is shared git thinks you have.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's a good point! Okay, I'll revert this doc change but remove that other line

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Gonna do that in other PR

@jsjoeio jsjoeio merged commit 505f07a into main Nov 1, 2022
@jsjoeio jsjoeio deleted the jsjoeio/minor-release-changes branch November 1, 2022 17:16
jsjoeio added a commit that referenced this pull request Nov 1, 2022
jsjoeio added a commit that referenced this pull request Nov 2, 2022
* chore: bump version to 4.8.2

* chore: update CHANGELOG

* docs: add back line in publishing release

See #5732 (comment)

* Revert "chore: bump version to 4.8.2"

This reverts commit 5d70994.

* fixup: use 4.8.2-rc.1

* docs: add release candidate notes

* refactor: warn plugin range incompatibble

* chore: bump version 4.8.2
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.

[Chore]: Use consistent artifact download workflow
2 participants