[3.5] Merge pull request 'fix-release-manifests-appsco' (#374) #375

Open
amorgante wants to merge 1 commits from amorgante-patch-1 into 3.5
Owner

Reviewed-on: #374
Reviewed-by: Nicolas Belouin nbelouin@noreply.src.opensuse.org

Reviewed-on: https://src.opensuse.org/suse-edge/Factory/pulls/374 Reviewed-by: Nicolas Belouin <nbelouin@noreply.src.opensuse.org>
amorgante added 1 commit 2026-01-29 15:22:51 +01:00
Merge pull request 'fix-release-manifests-appsco' (#374)
Some checks failed
Check Release Manifest Local Charts Versions / Check Release Manifest Local Charts Versions (pull_request) Successful in -34s
Build PR in OBS / Build PR in OBS (pull_request_target) Failing after -33s
f94144b969
Reviewed-on: #374
Reviewed-by: Nicolas Belouin <nbelouin@noreply.src.opensuse.org>
amorgante requested review from nbelouin 2026-01-29 15:23:13 +01:00
amorgante requested review from steven.hardy 2026-01-29 15:23:13 +01:00
amorgante requested review from dprodanov 2026-01-29 15:23:23 +01:00
steven.hardy changed title from Merge pull request 'fix-release-manifests-appsco' (#374) to [3.5] Merge pull request 'fix-release-manifests-appsco' (#374) 2026-01-29 16:06:42 +01:00
nbelouin approved these changes 2026-01-30 16:50:30 +01:00
Owner

@amorgante in future please can you use a personal fork instead of branching the main repo? Thanks!

Regarding the change, I think it's fine to change for 3.5.1 but not the already released 3.5.0 - so perhaps we can bump the version now to make that clear?

@amorgante in future please can you use a personal fork instead of branching the main repo? Thanks! Regarding the change, I think it's fine to change for 3.5.1 but not the already released 3.5.0 - so perhaps we can bump the version now to make that clear?
Owner

We don't re-release without changing the version, it's usually part of the release process (so for 3.5.1) to bump that number at this point, it can be done before though, but merging this won't change the released 3.5.0 manifest.

BTW, @amorgante I noticed this on main branch, but the ' around the uri are not needed and will get removed by the pre-commit hook at some point (it got removed on main branch with #383)

We don't re-release without changing the version, it's usually part of the release process (so for 3.5.1) to bump that number at this point, it can be done before though, but merging this won't change the released 3.5.0 manifest. BTW, @amorgante I noticed this on main branch, but the `'` around the uri are not needed and will get removed by the pre-commit hook at some point (it got removed on main branch with #383)
Some checks failed
Check Release Manifest Local Charts Versions / Check Release Manifest Local Charts Versions (pull_request) Successful in -34s
Build PR in OBS / Build PR in OBS (pull_request_target) Failing after -33s
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin amorgante-patch-1:amorgante-patch-1
git checkout amorgante-patch-1
Sign in to join this conversation.
No Label
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: suse-edge/Factory#375