Repository navigation
Page: changelog, release notes v0.1.0 and v0.2.1 quoted - #36
Closed
fosterstack-admin wants to merge 3 commits into
Closed
fosterstack-admin wants to merge 3 commits into
fosterstack-admin wants to merge 3 commits into
Conversation
Deploying www with
|
| Latest commit: |
6424a32
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8bf0affd.www-4rw.pages.dev |
| Branch Preview URL: | https://www-changelog.www-4rw.pages.dev |
Contributor
Author
|
folded into #48 |
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.
Fallback item from the advisor's message: /changelog quoting the cache repo's GitHub release notes verbatim (v0.1.0 commit list + its evidence note, v0.2.1 note). Facts: gh release list shows only v0.1.0 and v0.2.1 published; the v0.2.0 Release run concluded failure, so the page says no release was published for v0.2.0.
DECISION FOR THE ADVISOR: the v0.1.0 note (quoted as published, it is already public on GitHub) states v0.1.0's published images were not scanned before publication, being a separate build of the same commit. That is true for v0.1.0 and is not the current pipeline, but it is a visible 'gap' sentence on our own site. Keep it (honest, verbatim) or drop the v0.1.0 section? HOLD for owner cold-read either way.