Dummy release v3.2.x #44
Closed
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
Also note that a table column applies to >= 3.1 instead of just 3.1, and add an entry in the release history table.
dev: Validate src/oas.md
dev: schema tests use src/schemas/validation
dev: update from main
dev: update schema.yaml in src
v3.2-dev: update from dev
* add oauth2MetadataUrl Signed-off-by: Axel Nennker <[email protected]> * update anchor Signed-off-by: Axel Nennker <[email protected]> --------- Signed-off-by: Axel Nennker <[email protected]>
Migrate relevant 3.2 commits to the new branch structure
Signed-off-by: Vincent Biret <[email protected]>
Co-authored-by: Ralf Handl <[email protected]>
Co-authored-by: Ralf Handl <[email protected]>
Signed-off-by: Vincent Biret <[email protected]>
Co-authored-by: Vladimír Gorej <[email protected]>
Signed-off-by: Vincent Biret <[email protected]>
Co-authored-by: Vladimír Gorej <[email protected]>
Signed-off-by: Vincent Biret <[email protected]>
…m/baywet/OpenAPI-Specification into feat/url-template-anbf-to-3-2-dev
Configure deploydir based on branch name Check branch name for conformance to vX.Y.Z structure * deploy to /deploy/oas/$version if branch name is conformant * deploy to /deploy-preview if branch name is non-conformant Perform only one traversal of schemas structure Remove intermediate data structures (datesHash, sedCmd)
Update schema-publish.sh
Remove yaml2json
dev: update from main
v3.2-dev: update from dev
…ject-fields 3.2 schema: new fixed fields in Security Scheme Object
dev: update from main
v3.2-dev: update from dev
v3.2-dev: update from dev
…or-message dev: fix error message in schema-publish.sh
v3.2-dev: update from dev
Move old schemas to _archive_
Sync dummy rel from main
4 tasks
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.
Caution
Do not merge, this is for demo/test purposes only!
This PR shows that the steps described in OAI#4278 work.
It also shows that some infrastructure files on
mainare still out of sync withdev:CONTRIBUTING.md- will be fixed by main: sync CONTRIBUTING.md from dev OAI/OpenAPI-Specification#4436schema-publishworkflow and scripts - sync PR neededvalidate-markdownworkflow andpackage.jsonscripts - sync PR needed(not syncing these is also fine, they will then be synced when releasing v3.2.0 or v3.1.2)