You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Manifest location and content before the Dependabot update
No response
dependabot.yml content
# To get started with Dependabot version updates, you'll need to specify which# package ecosystems to update and where the package manifests are located.# Please see the documentation for all configuration options:# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updatesversion: 2registries:
nuget-code-artifact:
type: nuget-feedurl: https://REDACTED.d.codeartifact.eu-west-2.amazonaws.com/nuget/team-packages/v3/index.jsonusername: awspassword: ${{secrets.CODE_ARTIFACT_TOKEN_PRIVATE_REPOS}}private-github-actions:
type: giturl: https://github.comusername: x-access-tokenpassword: ${{secrets.PRIVATE_GITHUB_ACTIONS_TOKEN}}tf-cloud:
type: terraform-registryurl: https://app.terraform.iotoken: ${{secrets.DEPENDABOT_TF_CLOUD}}updates:
- package-ecosystem: "nuget"directory: "/"# Location of package manifestsregistries:
- nuget-code-artifactschedule:
interval: "daily"labels:
- "flag:dependencies"open-pull-requests-limit: 10
- package-ecosystem: "github-actions"directory: "/"# Location of package manifestsregistries:
- private-github-actionsschedule:
interval: "daily"labels:
- "flag:dependencies"
- package-ecosystem: "terraform"directory: "/deploy/bucket"# Location of package manifestsregistries: "*"schedule:
interval: "daily"labels:
- "flag:dependencies"
- package-ecosystem: "terraform"directory: "/deploy/lambda"# Location of package manifestsregistries: "*"schedule:
interval: "daily"labels:
- "flag:dependencies"
Updated dependency
No response
What you expected to see, versus what you actually saw
I have a private repository in my organisation that I put my shared workflows in. These are used across many projects successfully.
I recently published a new tag version 1.0.0.8 of the repository.
Dependabot created a PR to update this. It updated every instance of each shared workflow except one. This has remained on the previous tag. This exact behaviour is replicated on every repository that uses these shared workflows.
I would expect that they all get updated at the same time.
Is there an existing issue for this?
Package ecosystem
GitHub Actions
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
Updated dependency
No response
What you expected to see, versus what you actually saw
I have a private repository in my organisation that I put my shared workflows in. These are used across many projects successfully.
I recently published a new tag version 1.0.0.8 of the repository.
Dependabot created a PR to update this. It updated every instance of each shared workflow except one. This has remained on the previous tag. This exact behaviour is replicated on every repository that uses these shared workflows.
I would expect that they all get updated at the same time.
Successfully updated workflow (blocked-issue.yml):
Unsuccessfully updated workflow (static-analysis.yml):
If I run dependabot again it reports that this dependency is up to date.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: