Changelog/release notes visibility #8501
cy6erskunk
started this conversation in
Suggest an Idea
Replies: 1 comment 2 replies
-
The app contains a migration script to make it invisible there, and we plan to one day raise Pull Requests to migrate the config in each repo too. Currently the validator is strict and doesn't perform the migration before validating, but we plan to fix/improve that. In the end, the only time you should need to know about migrated params in future is when you get a PR saying to migrate you config . |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've just accidentally found that
packageRules.packageNames
is now considered an invalid config option according to therenovate-config-validator
.It seems to be working in the GitHub app, so I checked the docs, but there's no
packageNames
field description anymore.I did some searching to find the release and learned from the #6939 about #6805.
Is there any place where this type of changes could be tracked?
Is there a way to learn which version is now deployed in the GitHub app?
Would it be possible to preseve some information about deprecated config options?
Beta Was this translation helpful? Give feedback.
All reactions