fix(optimizely): configure release automation - #214
Open
yasaichi wants to merge 1 commit into
Open
Conversation
The Optimizely provider was added without the Release Please package and manifest entries required for new providers. Without them, provider changes cannot participate in the repository's automated release flow. Signed-off-by: Yuichi Sato <949545+yasaichi@users.noreply.github.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: Comment |
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.
Summary of Changes
release-please-config.json.release-please-manifest.jsonCONTRIBUTING.mdThe Optimizely provider was added in #128, but its Release Please configuration appears to have been omitted. Existing providers, including OFREP, are registered in both files so their releases can be automated.
component_owners.ymlalso currently lacks an Optimizely entry. This PR intentionally leaves it unchanged because ownership assignment is better handled by maintainers.Type of Change
Testing
0.1.0version matches the manifestgit diff --checkRSpec and RuboCop were not run because this change only updates Release Please JSON configuration and does not change Ruby code.
Checklist
bundle exec rspec) — not run; configuration-only changebundle exec rubocop) — not run; no Ruby changesgit commit -s)