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 please workflow on main branch errors "could not find changelog entry corresponding to release" #221

Closed
gobengo opened this issue Feb 10, 2023 · 3 comments

Comments

@gobengo
Copy link
Contributor

gobengo commented Feb 10, 2023

@gobengo
Copy link
Contributor Author

gobengo commented Feb 10, 2023

when it errors it says

✔ Found version 4.1.1 for packages/principal in .github/release-please-manifest.json at 36ab6fd of main

Notably that commit is from the botched release and is no long in main.
36ab6fd

I'm deleting tags that have it (which were git tags for semvers that never made it to npm)

@gobengo
Copy link
Contributor Author

gobengo commented Feb 10, 2023

duplicates #211

@gobengo
Copy link
Contributor Author

gobengo commented Feb 10, 2023

I'm deleting tags that have it (which were git tags for semvers that never made it to npm)

that didn't fix it, but I did do it.

I merged #210

  • which update release-manifest.json versions from 4.1.0 (before botched 4.1.1) to 4.2.3 (after) and that seemes to have fixed the error described above

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

No branches or pull requests

1 participant