-
Notifications
You must be signed in to change notification settings - Fork 9.1k
dev: update from main #4392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev: update from main #4392
Conversation
to circumvent puppeteer problem on Ubuntu > 22
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] <support@github.com>
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] <support@github.com>
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
@ralfhandl does this need a second approval or is there another reason we didn't merge yet? |
You are right, I could argue that this PR only changes infrastructure and is covered by our decision that these only require a single reviewer, same as dependable PRs. And I'd be fine by doing that in the future. The catch here is that this PR was created by a workflow that has itself not yet been approved and merged into main. |
Ah, got it. The other one should be reviewed first. |
main: minimalistic check for changes to `versions` and `schemas` folder
main: new workflow that syncs main to dev
Changes to infrastructure and its documentation only. |
Merge
main
intodev
.