Repository navigation
chore: move publish config to the release key - #11
Merged
Merged
Conversation
hyperi-ci renamed publish.enabled to release.enabled and no longer reads publish.target or build.type, so every CI run printed a deprecation warning for them.
|
Released in v3.5.2 -- https://github.com/hyperi-io/logreducer/releases/tag/v3.5.2 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
hyperi-ci renamed
publish.enabledtorelease.enabled, and no longer readspublish.target(orbuild.type). Every CI run printed a deprecation warning for each one, and those warnings land in #alerts-build.publish:becomesrelease:, same valuetarget: oss/build.typelines goNothing changes in what gets built or released. Done when the Quality job runs with no renamed-key warning.