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: 4.5.0 #5308

Merged
merged 10 commits into from
Jul 1, 2022
Merged

release: 4.5.0 #5308

merged 10 commits into from
Jul 1, 2022

Conversation

jsjoeio
Copy link
Contributor

@jsjoeio jsjoeio commented Jun 29, 2022

This PR is to generate a new release of code-server at v4.5.0

Screenshot

image

TODOs

Follow "Publishing a release" steps in ci/README.md

  • publish release and merge PR
  • update the AUR package
  • create issue to fix e2e test

Fixes #5307

Note
GitHub changed some validation around tags/branches. We need the branch to be different than the tag i.e. v4.5.0

We had to do this a little differently. @Emyrk and I agreed we can merge this PR, delete the branch and then publish the release.

@jsjoeio jsjoeio self-assigned this Jun 29, 2022
@jsjoeio jsjoeio requested a review from a team June 29, 2022 21:12
@github-actions
Copy link

github-actions bot commented Jun 29, 2022

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

@codecov
Copy link

codecov bot commented Jun 29, 2022

Codecov Report

Merging #5308 (b23c398) into main (55cfba8) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #5308    /-   ##
=======================================
  Coverage   72.47%   72.47%           
=======================================
  Files          30       30           
  Lines        1671     1671           
  Branches      367      367           
=======================================
  Hits         1211     1211           
  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 55cfba8...b23c398. Read the comment docs.

@jsjoeio jsjoeio temporarily deployed to npm June 29, 2022 21:17 Inactive
@github-actions
Copy link

github-actions bot commented Jun 29, 2022

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

  • Last publish status: success
  • Commit: b23c398

To install in a local project, run:

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

To install globally, run:

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

@jsjoeio jsjoeio temporarily deployed to npm June 29, 2022 21:37 Inactive
@jsjoeio jsjoeio temporarily deployed to npm June 29, 2022 23:30 Inactive
I'm not sure what changed in the latest version but without setting
VSCODE_DEV=1, code-server won't load. This fixes that.
@jsjoeio jsjoeio temporarily deployed to npm June 30, 2022 21:14 Inactive
@jsjoeio jsjoeio temporarily deployed to npm June 30, 2022 21:50 Inactive
@jsjoeio jsjoeio temporarily deployed to npm June 30, 2022 22:06 Inactive
@jsjoeio jsjoeio temporarily deployed to npm June 30, 2022 22:42 Inactive
@jsjoeio jsjoeio temporarily deployed to npm July 1, 2022 00:08 Inactive
I am not sure why this is passing locally and failing CI. I need to
further investigate this since it fails depending on where you test.
@jsjoeio jsjoeio temporarily deployed to npm July 1, 2022 16:52 Inactive
@jsjoeio jsjoeio marked this pull request as ready for review July 1, 2022 17:56
const element = await codeServerPage.page.waitForSelector(
`div[role="dialog"] >> text=code-server: ${isDevMode ? "Unknown" : "v" version}`,
)
const element = await codeServerPage.page.waitForSelector(`div[role="dialog"] >> text=code-server`)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I spent half a day trying to debug this. The dialog shows the version as expected but running locally vs in CI results in different outcomes. I will fix this next sprint: #5312

1. Run `yarn release:prep` and type in the new version (e.g., `3.8.1`)
1. GitHub Actions will generate the `npm-package`, `release-packages` and
`release-images` artifacts. You do not have to wait for this step to complete
before proceeding.
1. Run `yarn release:github-draft` to create a GitHub draft release from the
template with the updated version.
template with the updated version. Make sure to update the `CHANGELOG.md`.
1. Bump chart version in `Chart.yaml`.
Copy link
Member

Choose a reason for hiding this comment

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

lot of step 1s here 😄

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah yes, that's intentional! That way if you re-order, you don't have to go renumber them.

🖼️ rendered on GitHub

Source

Copy link
Member

Choose a reason for hiding this comment

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

TIL! Thanks for the link!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was trying to find the specific place but I think it's this:

(b) if the list item is ordered, the start number must be 1.

Someone from Coder taught me it actually!

@jsjoeio jsjoeio temporarily deployed to npm July 1, 2022 19:54 Inactive
@jsjoeio jsjoeio merged commit 9ad0d9e into main Jul 1, 2022
@jsjoeio jsjoeio deleted the v4.5.0 branch July 1, 2022 20:45
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]: release 4.5.0
2 participants