Repository navigation
Use canonical flycanon installation and source references - #12
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
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.
forge now installs the required flycanon SDK and managed server from fireflyframework/flycanon. Package metadata, lockfile, standalone distribution validation and knowledge/release documentation use the canonical repository. Versions and release checksums remain unchanged.
Validation: all five required canonical flycanon downloads match their published digests; locked dependency resolution and fresh installation passed, as did seven distribution tests, Ruff/format, strict MkDocs compilation, 18 configured documentation tests and discovery of all55 pages/social cards. Existing Studio and runtime behavior are unchanged.