Skip to content

[FEAT] - Update every collection release from this repo into requirements file of this repo #187

@patrick-hermann-sva

Description

@patrick-hermann-sva

can you create a renovate config format format like:

file in repo:

github releases:

release title:
release for sthings-container-25.1.1019.tar.gz
asset:
sthings-container-25.1.1019.tar.gz

dl link https://github.com/stuttgart-things/ansible/releases/download/sthings-container-25.1.1019.tar.gz/sthings-container-25.1.1019.tar.gz

if newer version from same schema is releases pr

To create a Renovate configuration that automatically handles updates for a specific format involving GitHub releases, you can use Renovate's versioning feature, combined with GitHub releases integration. This will allow Renovate to create a pull request (PR) whenever a newer version of the file is available (e.g., sthings-container-25.1.1019.tar.gz), and the version pattern is based on your schema.

Renovate Configuration:
Here is an example renovate.json configuration file for your scenario. The idea is to use GitHub releases integration to track the asset file's version and automatically update it in your repository when a new release is published.

{
  "extends": [
    "config:base"
  ],
  "packageRules": [
    {
      "managers": ["regex"],
      "matchPaths": ["**/file-in-repo.txt"],  // Path to the file containing the versioned URL
      "matchStrings": [
        "https://github.com/stuttgart-things/ansible/releases/download/sthings-container-(\\d+\\.\\d+\\.\\d+\\.\\d+)/sthings-container-\\1\\.tar\\.gz"
      ],
      "updateTypes": ["minor", "patch"],  // Update only minor and patch versions
      "versioning": "regex",
      "registryUrls": ["https://github.com/stuttgart-things/ansible/releases"],  // GitHub releases URL
      "depType": "devDependencies"
    }
  ],
  "versioning": "regex",
  "automerge": true
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions