Repository navigation
Prepare Foreman 1.1.0-rc.1: working installs and persistent runtime - #5
Merged
Merged
Conversation
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
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
Type of Change
Layer Affected
Canonical content references, command registration, modes, implementation tracking, plugin adapters and bundles, npm CLI, maintenance scripts and release tooling. Most added lines are generated, committed plugin resources needed for installation directly from Git.
Testing
Release status
This is an explicit prerelease. Final live advisory quality acceptance remains pending: earlier exploratory answers included unsupported causal claims, invented targets and language drift. Stronger instructions are included, but the complete final regression has not passed. A live Codex model session is also unverified.
The release candidate uses npm's
nextchannel when published. The stablelatestchannel remains 1.0.0. npm publishing requires a maintainer session or the documented trusted-publisher configuration; the public GitHub tarball is independently installable.