Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: surface environment variable to indicate Change level #6

Merged

Conversation

jamietanna
Copy link
Contributor

As noted in #5, it would be useful for Goreleaser templates to be able
to understand the different semver changes introduced in the release.

This exposes a variable if the change is detected, allowing a consumer
to use something like the below to conditionally handle the presence
(and non-zero contents), such as:

{{ if .Env.GOSEMREL_MAJOR }} ... {{ end }}

Closes #5.

As noted in go-semantic-release#5, it would be useful for Goreleaser templates to be able
to understand the different semver changes introduced in the release.

This exposes a variable if the change is detected, allowing a consumer
to use something like the below to conditionally handle the presence
(and non-zero contents), such as:

    {{ if .Env.GOSEMREL_MAJOR }} ... {{ end }}

Closes go-semantic-release#5.
@christophwitzko
Copy link
Member

Hi @jamietanna, thank you so much for this contribution! I will merge it once the CI passes ✅

@christophwitzko christophwitzko merged commit 68084e1 into go-semantic-release:main Jan 18, 2024
2 of 3 checks passed
@jamietanna jamietanna deleted the feature/hooks-env branch January 19, 2024 16:15
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.

Question: Making it clear to goreleaser whether there are breaking changes
2 participants