Problem with pinDevDependencies and devcontainers #29604
Replies: 2 comments 2 replies
-
Hi there, Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues. To get started, please read our guide on creating a minimal reproduction. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
lucasfijen
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
I think I found a bug
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Azure devops
Please tell us more about your question or problem
Hi,
I'm running into an issue when using the
config:best-practices
extends in combination with devcontainers.It seems like the
pinDevDependencies
tag that is part of theconfig:best-practices
tries to pin versions in thedevcontainer.json
, but these will also attempt to add sha256 tags to the links in the features of thedevcontainer.json
, which doesnt support that (it is supported for theimage
).Examples:
I've also set up an example repository: lucasfijen/devcontainer_renovate_bug#1
So for example the following
devcontainer.json
:Will be receiving a PR with the following changes:
The problem is, this isn't supported in vscode devcontainers for the features and will make the build of your devcontainer fail.
renovate.json:
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions