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

Investigate and document 'next version' testing of example apps #19138

Closed
jennifer-shehane opened this issue Nov 29, 2021 · 1 comment · Fixed by #19157
Closed

Investigate and document 'next version' testing of example apps #19138

jennifer-shehane opened this issue Nov 29, 2021 · 1 comment · Fixed by #19157
Assignees

Comments

@jennifer-shehane
Copy link
Member

We have a process around testing 'example' apps for breaking change releases, so that we can update example apps ahead of release and test all of them with upcoming breaking changes.

Each time we do a breaking release, the team is confused about how this works because it is poorly documented and the logic exists across several repositories and is unclear on how the coordinate.

We want this clearly documented so that engineers and DX know how to coordinate this in the future. Especially:

  • What to name branches on example apps
  • Which example apps this works on
  • How to set 'next version'
@cypress-bot
Copy link
Contributor

cypress-bot bot commented Dec 2, 2021

The code for this is done in cypress-io/cypress#19157, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

@cypress-bot cypress-bot bot removed the stage: needs review The PR code is done & tested, needs review label Dec 2, 2021
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 a pull request may close this issue.

3 participants