Repository navigation
chore(release): promote 0.2.1 release request - #32
Merged
Merged
Conversation
…cture (#27) The three Playground families now plan a change to existing infrastructure: base is the existing platform planned with no changes, and head is the proposed change planned against the same state. - Commerce platform (Azure): AKS monitoring moves to a new platform Log Analytics workspace and the legacy blob webhook pipeline is retired. - Event-driven platform (Azure): scored claims go to a new priority queue and an Event Grid subscription replaces the scheduled poller. - Shared data platform (Google Cloud): raw events are pushed to a new Cloud Run consumer with a dead-letter topic. The Forms, the reference runtime Forms, the documentation figures and tour, and the documentation that quotes these samples follow the new plans. The AWS presentation catalog maps its Rules and Concepts to official AWS Architecture Icon identities, and five Azure Rules move to official Azure icons.
- Move each Dialect's reviewed scenarios to fixtures/expectations and the plan fixture inventory to fixtures/inventory.json, unchanged. - Move the provider registry equivalence beside dialects.json. - Remove the research snapshots and spike notes that no script generates, reads or refreshes; git history keeps them. - The validator accepts only the inventory and one expectations file per official Dialect beside the fixtures, and checks their fixture and Rule references.
…icons (#28) - The Google Cloud presentation catalog maps 198 of 217 Rules and 58 of 70 Concepts to google/* identities: a core product shows its own icon and other products the icon of their category, as the Google Cloud product icon guide assigns them; Cloud Source Repositories draws the Developer Tools category icon. - Rules whose product has no icon in the library, such as the Google Cloud project, keep a neutral symbol. - The Playground presentation files and their digests follow the catalog.
The pinned pull request build is no longer published, so runtime lanes failed to download it. Pin v0.2.0 by its archive digests, extract each pinned version into its own directory and regenerate the reference Playground fixtures with the 0.2.0 binary.
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.
Change
Fast-forward main to the reviewed release request on dev: Rootform 0.2.1, Engine e697b5fe84a3b377ba2d8a209e40046f8660f70b, the 0.2.1 changelog and documentation, and Playground Forms regenerated with the 0.2.1 build. It also carries the CI reference runtime moved to the published 0.2.0 release.
Validation
PR #30, PR #31 and PR #33 passed public repository boundary, Contribution delivery and CodeQL on their exact heads.
bun scripts/prepare-release.ts --checkreports version 0.2.1, tag v0.2.1 and that Engine commit. The promotion workflow fast-forwards main after this pull request's required check succeeds.