chore: release v0.13.0 #196

Merged

jwilger merged 1 commit from release/v0.13.0 into main 2026-05-14 13:01:06 -07:00

Conversation 4 Commits 1 Files changed 3 +24 -10

jwilger commented 2026-05-14 07:24:48 -07:00

Owner

Copy link

Prepare release v0.13.0.

CI publishes release-candidate Docker and binary package links on the PR; final release entries are created only after merge to main.

Prepare release v0.13.0. CI publishes release-candidate Docker and binary package links on the PR; final release entries are created only after merge to main.

jwilger added 1 commit 2026-05-14 07:24:48 -07:00

chore: release v0.13.0 21d160d987

auto-review approved these changes 2026-05-14 07:31:23 -07:00

Dismissed

auto-review left a comment

Copy link

This PR prepares for the release of version 0.13.0 by updating the version numbers in the Cargo files and adding a new entry to the CHANGELOG. The changes are straightforward and appear safe to merge.

This PR prepares for the release of version 0.13.0 by updating the version numbers in the Cargo files and adding a new entry to the CHANGELOG. The changes are straightforward and appear safe to merge.

jwilger force-pushed release/v0.13.0 from 21d160d987 to 1e4a7b7726 2026-05-14 07:37:47 -07:00 Compare

jwilger dismissed auto-review's review 2026-05-14 07:37:47 -07:00

Reason:

New commits pushed, approval review dismissed automatically according to repository settings

auto-review approved these changes 2026-05-14 07:41:49 -07:00

Dismissed

auto-review left a comment

Copy link

This PR updates the CI and release workflows to use a release-candidate tag for Docker images and modifies the artifact handling process to rely on pre-reviewed binaries. The changes appear to streamline the release process but require verification to ensure they align with the project's release strategy.

Walkthrough

Δ since 21d160d:

• CI Workflow Changes

  • Updated the rc_tag to use a release-candidate tag instead of a versioned tag.
  • Removed the step to update the PR description with artifact links.

• Release Publish Workflow Changes

  • Added a step to resolve trusted release publication tools.
  • Changed from building Linux binary artifacts to downloading reviewed artifacts.

• Changelog Update

  • Added an entry for version 0.13.0, noting the promotion of release-candidate artifacts.

• Test Updates

  • Updated tests to reflect changes in artifact handling and tagging strategy.

This PR updates the CI and release workflows to use a `release-candidate` tag for Docker images and modifies the artifact handling process to rely on pre-reviewed binaries. The changes appear to streamline the release process but require verification to ensure they align with the project's release strategy. ## Walkthrough ### Δ since 21d160d: - **CI Workflow Changes** - Updated the `rc_tag` to use a `release-candidate` tag instead of a versioned tag. - Removed the step to update the PR description with artifact links. - **Release Publish Workflow Changes** - Added a step to resolve trusted release publication tools. - Changed from building Linux binary artifacts to downloading reviewed artifacts. - **Changelog Update** - Added an entry for version 0.13.0, noting the promotion of release-candidate artifacts. - **Test Updates** - Updated tests to reflect changes in artifact handling and tagging strategy.

jwilger force-pushed release/v0.13.0 from 1e4a7b7726 to 7f1ef872e0 2026-05-14 11:13:20 -07:00 Compare

jwilger dismissed auto-review's review 2026-05-14 11:13:20 -07:00

Reason:

New commits pushed, approval review dismissed automatically according to repository settings

auto-review approved these changes 2026-05-14 11:17:10 -07:00

Dismissed

auto-review left a comment

Copy link

This PR updates the CI workflow to use the PR title instead of the user login for identifying release PRs, and adjusts the changelog and test scripts accordingly. The changes appear safe to merge, but ensure that the new logic aligns with the intended release process.

This PR updates the CI workflow to use the PR title instead of the user login for identifying release PRs, and adjusts the changelog and test scripts accordingly. The changes appear safe to merge, but ensure that the new logic aligns with the intended release process.

jwilger force-pushed release/v0.13.0 from 7f1ef872e0 to 2a33e3c59f 2026-05-14 12:42:44 -07:00 Compare

jwilger dismissed auto-review's review 2026-05-14 12:42:44 -07:00

Reason:

New commits pushed, approval review dismissed automatically according to repository settings

auto-review approved these changes 2026-05-14 12:46:33 -07:00

auto-review left a comment

Copy link

The PR updates CI workflows to use the supported --creds flag for skopeo inspect, ensuring compatibility with current standards. The changes appear safe to merge.

Walkthrough

• CI Workflow Changes:
  • Updated .forgejo/workflows/ci.yml and .forgejo/workflows/release-publish.yml to replace deprecated --src-creds with --creds for skopeo inspect commands.
  • This change ensures that the workflows remain compatible with the latest skopeo standards and avoid potential issues with deprecated flags.
• Permission System Configuration:
  • Expanded the config.json to include more specific path permissions and restrictions, enhancing security and flexibility in file access.
• Tests:
  • Added new test cases in ci_pr_artifacts_test.sh and publish_workflow_test.sh to verify the correct usage of skopeo inspect with the --creds flag.

The PR updates CI workflows to use the supported `--creds` flag for `skopeo inspect`, ensuring compatibility with current standards. The changes appear safe to merge. ## Walkthrough - **CI Workflow Changes**: - Updated `.forgejo/workflows/ci.yml` and `.forgejo/workflows/release-publish.yml` to replace deprecated `--src-creds` with `--creds` for `skopeo inspect` commands. - This change ensures that the workflows remain compatible with the latest `skopeo` standards and avoid potential issues with deprecated flags. - **Permission System Configuration**: - Expanded the `config.json` to include more specific path permissions and restrictions, enhancing security and flexibility in file access. - **Tests**: - Added new test cases in `ci_pr_artifacts_test.sh` and `publish_workflow_test.sh` to verify the correct usage of `skopeo inspect` with the `--creds` flag.

.forgejo/workflows/ci.yml

Show resolved Hide resolved

auto-review commented 2026-05-14 12:46:33 -07:00

Owner

Copy link

🟡 Warning: The --src-creds flag is deprecated for skopeo inspect. Ensure that --creds is used consistently for authentication in all relevant commands.

🟡 **Warning:** The `--src-creds` flag is deprecated for `skopeo inspect`. Ensure that `--creds` is used consistently for authentication in all relevant commands.

jwilger marked this conversation as resolved

.forgejo/workflows/release-publish.yml

Show resolved Hide resolved

auto-review commented 2026-05-14 12:46:33 -07:00

Owner

Copy link

🟡 Warning: The --src-creds flag is deprecated for skopeo inspect. Ensure that --creds is used consistently for authentication in all relevant commands.

🟡 **Warning:** The `--src-creds` flag is deprecated for `skopeo inspect`. Ensure that `--creds` is used consistently for authentication in all relevant commands.

jwilger marked this conversation as resolved

jwilger merged commit 2e2d23c1d7 into main 2026-05-14 13:01:06 -07:00

jwilger deleted branch release/v0.13.0 2026-05-14 13:01:06 -07:00

jwilger referenced this pull request from a commit 2026-05-14 13:01:08 -07:00

chore: release v0.13.0 (#196)

Sign in to join this conversation.

Reviewers

No reviewers

auto-review

Labels

Clear labels   

bug

  

discussion

  

enhancement

  

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

wontfix

This won't be fixed

No labels

bug

discussion

enhancement

bug

duplicate

enhancement

help wanted

invalid

question

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Slipstream/auto_review!196

No description provided.