[pull] main from OAI:main #65
Open
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
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
Annotated enums and extended validation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 2.1.1 to 2.1.2. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v2.1.2/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: Ralf Handl <[email protected]> Co-authored-by: Kevin Swiber <[email protected]>
Bump vitest from 2.1.1 to 2.1.2
clarifies security requirements wording for 3.1.1
Co-authored-by: Ralf Handl <[email protected]> Co-authored-by: Kevin Swiber <[email protected]>
…ed in the "resolving relative URLs" section Co-authored-by: Ralf Handl <[email protected]>
This explicitly lists out the cases and notes which ones were (as far as we can recall) intended to behave like `$ref`, but could be reasonably read to behave like API URLs.
Co-authored-by: Ralf Handl <[email protected]>
Co-authored-by: Ralf Handl <[email protected]>
clarifies security requirements wording for 3.0.4 (port of #4123)
Per post-TDC call with Darrel.
Co-authored-by: Ralf Handl <[email protected]>
Co-authored-by: Ralf Handl <[email protected]>
Co-authored-by: Mike Kistler <[email protected]>
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.0.5 to 3.0.6. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v3.0.6/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bump vitest from 3.0.5 to 3.0.6
Run respec without sandbox
Describe spec and schema publishing process
main: update style-guide.md - consistent style for field names and values in YAML comments
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.0.6 to 3.0.7. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v3.0.7/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bump vitest from 3.0.6 to 3.0.7
Update Zoom UI screenshot for Raise Hand control
Update agenda.md
@lornajane's suggestion
New workflow to sync changes from main to dev via PRs
style guide: no requirements in "Examples" sections
Simple workflow to check for changes to files in schemas and versions folder
main: minimalistic check for changes to `versions` and `schemas` folder
Check in the whether the PR is an intra-repo sync PR or release PR and report "ok" for these. Conditions: - PR's `head` and `base` repo is `OAI/OpenAPI-Specification` and - `head` is `main` and `base` is `dev`, or - `head` is `dev` and `base` matches `v?.?-dev`, or - `head` matches `v?.?.?-rel` and `base` is `main`
main: new workflow that syncs main to dev
main: new workflow that syncs dev to vX.Y-dev
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.0.7 to 3.0.8. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v3.0.8/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…ow-some-PRs main: check-restricted-files.yaml reports ok for intra-repo PRs that are allowed to change these files
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )