Skip to content

🌱 Add release/0.3.z branch to config.yaml#38

Merged
carlosthe19916 merged 1 commit intomainfrom
carlosthe19916-patch-1
Jun 2, 2025
Merged

🌱 Add release/0.3.z branch to config.yaml#38
carlosthe19916 merged 1 commit intomainfrom
carlosthe19916-patch-1

Conversation

@carlosthe19916
Copy link
Copy Markdown
Contributor

No description provided.

@carlosthe19916 carlosthe19916 changed the title Add release/0.3.z branch to config.yaml 🌱 Add release/0.3.z branch to config.yaml Jun 2, 2025
@carlosthe19916 carlosthe19916 merged commit 1dcac08 into main Jun 2, 2025
5 of 6 checks passed
- color: fef2a0
description: This PR should be backported to release/0.2.z branch.
name: backport release/0.2.z
- color: c2e0c6
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally I'd prefer to have the same colors for all release related tags.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I can change it. However, notice that this configuration has no effect neither in the backend trustify repository neither in the helm chart repository.

https://github.com/trustification/release-tools/blob/main/pkg/config/config.yaml#L12-L26

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants