Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@ansmonjol
Copy link
Contributor

@ansmonjol ansmonjol commented Oct 10, 2025

Changing some options for renovabot after it ran few times.

  • increase the minimumReleaseAge value from 3 to 7.
    We know that recently there were some malicious upgrade from some packages. Even tho they have been catch fast let's be safe here. It also let time to the community to report some bugs and see of the version is "really" working
  • add "pinVersions": true
    Makes sure the version in package.json is pined and does not allow patch to be installed without them to be referenced in the package.json. Feel giving more control and we'll have renovate update the version in the package.json anyway
  • remove bumpVersion option
    It has not the effect I expected. Thought it would bump the package.json of the upgraded package when it has a new version. Otherwise it does update the root version of our package.json. Not sure about our strategy there and we may need to consider other aspects before starting to often bump our version

@ansmonjol ansmonjol self-assigned this Oct 10, 2025
@ansmonjol ansmonjol added the 🥷 chore This doesn't seem right label Oct 10, 2025
@ansmonjol ansmonjol force-pushed the renovate-adjustments branch from c8f2fe4 to 7e15cf4 Compare October 10, 2025 14:20
@ansmonjol ansmonjol requested a review from AllanMichay October 10, 2025 16:24
@ansmonjol ansmonjol enabled auto-merge (squash) October 10, 2025 16:27
@ansmonjol ansmonjol merged commit ea2952a into main Oct 10, 2025
8 checks passed
@ansmonjol ansmonjol deleted the renovate-adjustments branch October 10, 2025 16:32
ansmonjol added a commit that referenced this pull request Oct 10, 2025
Changing some options for renovabot after it ran few times.
- increase the `minimumReleaseAge` value from 3 to 7. 
We know that recently there were some malicious upgrade from some
packages. Even tho they have been catch fast let's be safe here. It also
let time to the community to report some bugs and see of the version is
"really" working
- add `"pinVersions": true`
Makes sure the version in package.json is pined and does not allow patch
to be installed without them to be referenced in the package.json. Feel
giving more control and we'll have renovate update the version in the
package.json anyway
- remove `bumpVersion` option
It has not the effect I expected. Thought it would bump the package.json
of the upgraded package when it has a new version. Otherwise it does
update the root version of our package.json. Not sure about our strategy
there and we may need to consider other aspects before starting to often
bump our version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🥷 chore This doesn't seem right

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants