-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
chore: Update release guide docker steps #23249
Conversation
These changes will test the docker image prior to making the new cypress release available. This will also ensure the docker image gets released very near to the npm package.
Thanks for taking the time to open a PR!
|
@@ -136,28 +136,33 @@ In the following instructions, "X.Y.Z" is used to denote the [next version of Cy | |||
- Merge any release-specific documentation changes into the main release PR. | |||
- You can view the doc's [branch deploy preview](https://github.com/cypress-io/cypress-documentation/blob/master/CONTRIBUTING.md#pull-requests) by clicking 'Details' on the PR's `netlify-cypress-docs/deploy-preview` GitHub status check. | |||
|
|||
13. Make the new npm version the "latest" version by updating the dist-tag `latest` to point to the new version: | |||
13. Create a PR for a new docker image in [`cypress-docker-images`](https://github.com/cypress-io/cypress-docker-images) under `included` for the new cypress version. Note: we use the base image with the Node version matching the bundled Node version. Instructions for updating `cypress-docker-images` can be found [here](https://github.com/cypress-io/cypress-docker-images/blob/master/CONTRIBUTING.md#add-new-included-image). Ensure the docker image is reviewed and has passing tests before preceeding. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved creating the docker PR to be before we make the new tag 'latest'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious, where do we find node version bundled with cypress?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's this: https://github.com/cypress-io/cypress/blob/develop/package.json#L220
It would be the version of node that electron ships.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and we update the package.json whenever we update electron
|
||
16. If needed, deploy the updated [`cypress-example-kitchensink`][cypress-example-kitchensink] to `example.cypress.io` by following [these instructions under "Deployment"](../packages/example/README.md). | ||
17. Merge the new docker image PR created in step 13 to release the image. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Release the docker container here.
These changes will test the docker image prior to making the new cypress release available. This will also ensure the docker image gets released very near to the npm package.
User facing changelog
n/a
Additional details
These changes will test the docker image prior to making the new cypress release available. This will also ensure the docker image gets released very near to the npm package.
Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?