chore: add 3.5.5 schema and update SCHEMAS.md #1223
Merged
Conversation
This file contains 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
|
No code changes, yet the file is different from 3.5.4? |
|
confirming that there are no changes to the generated code. |
dimaqq
approved these changes
Nov 28, 2024
Indeed, the Juju 3.5.5 schema adds the charm-rev field to ApplicationStatus, but there are no changes to the generated code because this field is present in the 3.6.0 schema that was previously added |
|
/merge |
3.5.5 schema adds the charm-rev field to ApplicationStatus, but there are no changes to the generated code because this field is present in the 3.6.0 schema that was previously added
james-garner-canonical
force-pushed
the
2024-11/chore/update-schemas
branch
from
870fca0 to
a22749c
Compare
|
/merge |
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.
Description
The Juju 3.5.5 schema adds the charm-rev field to ApplicationStatus, but there are no changes to the generated code because this field is present in the 3.6.0 schema that was previously added.
QA Steps
As there are no code changes in this PR, CI outcomes shouldn't be affected