mirror of
https://github.com/renovatebot/renovate.git
synced 2026-10-27 07:50:47 +00:00
1f3b3a9d56
feat(terragrunt): detect forgejo-tags datasource for git-tag sources detectGitTagDatasource() in the terragrunt manager only handled gitlab, bitbucket and gitea platforms, so Forgejo-hosted modules (e.g. codeberg.org) fell through to the generic git-tags datasource and lost release timestamps, sourceUrl and changelog data. Add a 'forgejo' case mapping to ForgejoTagsDatasource, mirroring the existing pattern in the github-actions manager's detectDatasource(). Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Currently by default, Terragrunt support is limited to Terraform registry sources and GitHub sources that include SemVer refs, e.g. like github.com/hashicorp/example?ref=v1.0.0.
You can create a custom versioning config to support non-SemVer references.
For example, if you want to reference a tag like module-v1.2.5, a block like this would work:
{
"terragrunt": {
"versioning": "regex:^((?<compatibility>.*)-v|v*)(?<major>\\d+)\\.(?<minor>\\d+)\\.(?<patch>\\d+)$"
}
}
Pinned Terragrunt dependencies like the following will get a PR whenever there is a newer version available:
terraform {
source = "github.com/hashicorp/example?ref=v1.0.0"
}
Terraform lockfiles
The Terragrunt manager supports lock file maintenance for .terraform.lock.hcl artifacts.
These artifacts will be updated if and only if the update type is lockFileMaintenance.