Publish nightly status.json under nightly/ instead of release-nightly/ - #93
Open
HereThereBeDragons wants to merge 1 commit into
Open
Publish nightly status.json under nightly/ instead of release-nightly/#93HereThereBeDragons wants to merge 1 commit into
HereThereBeDragons wants to merge 1 commit into
Conversation
1 task
marbre
approved these changes
Sep 7, 2026
Member
|
Btw, any way to test this in advance? |
Collaborator
Author
|
the unit tests in but yes, we need a pr check to run the unit tests and not just trust people run them locally |
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
3 participants
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.
Nightly
status.jsonfiles are now published undernightly/instead ofrelease-nightly/, aligning the directory name with therelease_typevalue of TheRock. This updates the producer, the consumer example, the docs, and the tests. Thelatest.json/latest_good.jsonpointers move with it.The existing
release-nightly/tree is left in place and will be removed in a follow-up PR, so this change is additive on the CI side.