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 notes ordering issue #5574

Closed
Tracked by #14138
wyardley opened this issue Feb 25, 2020 · 5 comments
Closed
Tracked by #14138

Release notes ordering issue #5574

wyardley opened this issue Feb 25, 2020 · 5 comments
Labels
core:changelogs Related to changelogs/release notes fetching priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:requirements Full requirements are not yet known, so implementation should not be started type:bug Bug fix of existing functionality worker:pr Related to non-onboarding PR creation or update

Comments

@wyardley
Copy link

wyardley commented Feb 25, 2020

What Renovate type are you using?
pro (self-hosted) - 18.x

Describe the bug
With internal (and now some external dependencies), sometimes we'll see release notes repeated, e.g., if there are two releases, the release notes for the most recent are repeated twice under each version.

This one doesn't seem to have GH releases, so maybe it's weirdness with NPM itself?
Compare this:
image
with
https://github.com/googleapis/nodejs-pubsub/blob/master/CHANGELOG.md
and
https://www.npmjs.com/package/@google-cloud/pubsub

Did you see anything helpful in debug logs?
n/a

To Reproduce

See repro:

Additional context
Will try to track down an example of the similar / same issue with an internal repo.

@JamieMagee JamieMagee added manager:npm package.json files (npm/yarn/pnpm) type:bug Bug fix of existing functionality labels Feb 26, 2020
@rarkins rarkins added needs-reproduction priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others labels Feb 29, 2020
@rarkins
Copy link
Collaborator

rarkins commented Mar 30, 2020

This might be resolved by #5807. If you can reproduce it in a public repo then I can test it with the CLI to confirm.

@ViralRuparel

This comment has been minimized.

@rarkins rarkins added the status:requirements Full requirements are not yet known, so implementation should not be started label Jan 12, 2021
@viceice
Copy link
Member

viceice commented Mar 5, 2021

@viceice viceice removed the manager:npm package.json files (npm/yarn/pnpm) label Mar 5, 2021
@viceice
Copy link
Member

viceice commented Mar 5, 2021

It's manager independend

@viceice viceice added the worker:pr Related to non-onboarding PR creation or update label Mar 5, 2021
@viceice
Copy link
Member

viceice commented Mar 8, 2021

Missing changelog at all here: renovatebot/github-action#538

Changelog is here: https://github.com/wagoid/commitlint-github-action/blob/master/CHANGELOG.md
Releases are empty.

@viceice viceice added the core:changelogs Related to changelogs/release notes fetching label Feb 10, 2022
@rarkins rarkins closed this as not planned Won't fix, can't repro, duplicate, stale Apr 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
core:changelogs Related to changelogs/release notes fetching priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:requirements Full requirements are not yet known, so implementation should not be started type:bug Bug fix of existing functionality worker:pr Related to non-onboarding PR creation or update
Projects
None yet
Development

No branches or pull requests

5 participants