Release automation for stable branches does not update version for root package
Open
Nobody has claimed this yet.
1. to develop
bug
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Steps to reproduce
- Checkout stable5.5
- Update a dependency manually
- Notice that version (of the mail app) is also changed
Expected behavior
Release automation should also update the lockfile properly
Actual behavior
https://github.com/nextcloud/mail/blob/66eb0066f52765039c1644467d8d892a14c8b52b/package-lock.json#L3
https://github.com/nextcloud/mail/blob/66eb0066f52765039c1644467d8d892a14c8b52b/package-lock.json#L9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect package-lock.json at the referenced lines on stable5.5 and trace the release automation that runs after a dependency is updated manually. Compare the root package version with the mail app version, then verify that the automation updates the lockfile consistently without changing the wrong version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100