Skip to content

chore(deps): update cplieger/ci action to v3 - #247

Closed
cplieger wants to merge 1 commit into
mainfrom
renovate/cplieger-ci-3.x
Closed

cplieger wants to merge 1 commit into
mainfrom
renovate/cplieger-ci-3.x

Conversation

@cplieger

@cplieger cplieger commented Oct 1, 2026 •

Copy link
Copy Markdown
Owner

This PR contains the following updates:

Package Type Update Change
cplieger/ci workflow major v2 → v3

Release Notes

cplieger/ci

v3.4.3

Compare Source

Dependencies
  • Update module github.com/cplieger/deadset to v1.11.0 (#​716)

v3.4.2

Compare Source

Dependencies
  • Update module github.com/cplieger/deadset-go to v1.26.0 (#​715)

v3.4.1

Compare Source

Dependencies

v3.4.0

Compare Source

Added
  • Add the two-branch release model and deadset dead-code checks (#​713)

v3.3.5

Compare Source

Dependencies
  • Update actions/setup-node action to v7.1.0 (#​711)

v3.3.4

Compare Source

Dependencies
  • Update module golang.org/x/exp to v0.0.0-20261007192929-f45ad48fbe92 (#​710)

v3.3.3

Compare Source

Dependencies
  • Update module golang.org/x/exp to v0.0.0-20261007180756-3d68b386da03 (#​709)

v3.3.2

Compare Source

Dependencies
  • Update actions/upload-artifact action to v7.0.2 (#​708)

v3.3.1

Compare Source

Dependencies
  • Update actions/download-artifact action to v8.0.2 (#​707)

v3.3.0

Compare Source

Added
  • Skip hand-written release bodies in the notes backfill
Changed
  • State synced-config comment rationale without unpublished docs
  • State the lint config's rationale without rollout history
Dependencies
Fixed
  • Stop the shared prettier config from formatting Markdown
Dependencies
  • Update module golang.org/x/exp to v0.0.0-20261005173118-76772065c9b0 (#​695)
Added
  • Skip the synced release workflow for repos with own publish
  • Fail an image release whose go.mod carries a major suffix
Changed
  • Require exhaustive switches over unions
Dependencies
  • Update dependency docker/buildx to v0.37.2 (#​684)
Dependencies
  • Update module golang.org/x/tools to v0.51.0 (#​681)
Dependencies
  • Update anchore/sbom-action action to v0.24.3 (#​678)
Fixed
  • Clone and discover repos without GraphQL in scheduled jobs
Added
  • Run a repo-owned image test suite in the docker job
Dependencies
  • Update dependency ruff to v0.16.10 (#​674)
Breaking changes
Publish a dev channel and promote to stable by fast-forward

The release pipeline now reads its channel from the
branch, and two inputs are gone.

  • A repo whose default branch is dev publishes pre-release versions
    (vX.Y.Z-dev.N, image tag :dev on GHCR, npm dist-tag dev, no
    GitHub Release) from every push to dev, and a stable version only
    when main is fast-forwarded to a dev commit. A repo whose default
    branch is main keeps today's behaviour.
  • release.yaml no longer accepts the skip_if_unchanged input.
    Remove it from any hand-maintained caller; a dispatch that still
    passes it fails with unexpected inputs.
  • docker-release.yaml requires the new channel input (dev or
    stable) and no longer accepts skip-if-unchanged.
  • The caller's release job needs statuses: write beside
    contents: write; the synced release.yml template carries it. A
    hand-maintained caller without it fails at the dev tag step.
  • A deployed repo on the dev channel must subscribe its deploy
    webhook to the registry_package event, because dev builds create
    no GitHub Release.
Added
  • [breaking] Publish a dev channel and promote to stable by fast-forward
  • Name a public repo that still releases from main
Dependencies

v3.2.1

Compare Source

Dependencies
  • Update module golang.org/x/exp to v0.0.0-20261005173118-76772065c9b0 (#​695)

v3.2.0

Compare Source

Added
  • Skip the synced release workflow for repos with own publish
  • Fail an image release whose go.mod carries a major suffix

v3.1.3

Compare Source

Changed
  • Require exhaustive switches over unions
Dependencies
  • Update dependency docker/buildx to v0.37.2 (#​684)

v3.1.2

Compare Source

Dependencies
  • Update module golang.org/x/tools to v0.51.0 (#​681)

v3.1.1

Compare Source

Dependencies
  • Update anchore/sbom-action action to v0.24.3 (#​678)
Fixed
  • Clone and discover repos without GraphQL in scheduled jobs

v3.1.0

Compare Source

Added
  • Run a repo-owned image test suite in the docker job

v3.0.1

Compare Source

Dependencies
  • Update dependency ruff to v0.16.10 (#​674)

v3.0.0

Compare Source

Breaking changes
Publish a dev channel and promote to stable by fast-forward

The release pipeline now reads its channel from the
branch, and two inputs are gone.

  • A repo whose default branch is dev publishes pre-release versions
    (vX.Y.Z-dev.N, image tag :dev on GHCR, npm dist-tag dev, no
    GitHub Release) from every push to dev, and a stable version only
    when main is fast-forwarded to a dev commit. A repo whose default
    branch is main keeps today's behaviour.
  • release.yaml no longer accepts the skip_if_unchanged input.
    Remove it from any hand-maintained caller; a dispatch that still
    passes it fails with unexpected inputs.
  • docker-release.yaml requires the new channel input (dev or
    stable) and no longer accepts skip-if-unchanged.
  • The caller's release job needs statuses: write beside
    contents: write; the synced release.yml template carries it. A
    hand-maintained caller without it fails at the dev tag step.
  • A deployed repo on the dev channel must subscribe its deploy
    webhook to the registry_package event, because dev builds create
    no GitHub Release.
Added
  • [breaking] Publish a dev channel and promote to stable by fast-forward
  • Name a public repo that still releases from main
Dependencies

Configuration

📅 Schedule: (in timezone Europe/Paris)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

@cplieger
cplieger force-pushed the renovate/cplieger-ci-3.x branch 2 times, most recently from 6fe8917 to 4f0bd7f Compare October 2, 2026 01:00
@cplieger cplieger changed the title chore(deps): update cplieger/ci action to v3 chore(deps): update cplieger/ci action to v3 - autoclosed Oct 2, 2026
@cplieger cplieger closed this Oct 2, 2026
@cplieger
cplieger deleted the renovate/cplieger-ci-3.x branch October 2, 2026 02:00
@cplieger cplieger changed the title chore(deps): update cplieger/ci action to v3 - autoclosed chore(deps): update cplieger/ci action to v3 Oct 2, 2026
@cplieger cplieger reopened this Oct 2, 2026
@cplieger
cplieger force-pushed the renovate/cplieger-ci-3.x branch 16 times, most recently from 9ba0021 to 69b1d86 Compare October 8, 2026 08:00
@tribble-trouble
tribble-trouble Bot force-pushed the renovate/cplieger-ci-3.x branch from 69b1d86 to edd155c Compare October 8, 2026 09:03
@tribble-trouble
tribble-trouble Bot force-pushed the renovate/cplieger-ci-3.x branch from edd155c to 6f6fb2a Compare October 8, 2026 11:03
@cplieger

cplieger commented Oct 8, 2026

Copy link
Copy Markdown
Owner Author

Superseded by the v3 repoint in cplieger/ci#718, which moves every caller to v3 by sync. Closing.

@cplieger cplieger closed this Oct 8, 2026
@tribble-trouble

Copy link
Copy Markdown
Contributor

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant