-
Notifications
You must be signed in to change notification settings - Fork 9.1k
3.1.1: update from main #4074
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
3.1.1: update from main #4074
Conversation
merging per today's TDC call
Merging per today's TDC call
merging per today's TDC call
Workflows run from the workflow file on main, even when they run on branches. But just running "npm i" or a command like "npx" that also installs packages uses the package.json file from the branch. Rather than attempt to keep the branch package files up-to-date (which would _quadruple_ the number of update PRs, adding three branch update PRs for every dependabot PR), let's just checkout the package.json from main whenver we run. The other workflows only run on main - these two are the ones that run on branches.
Always checkout JavaScript environment from main
…ekeeping time (OAI#3522) * Remove old backlog agenda and unused tag filters from weekly meeting agenda, add housekeeping entry * Update agenda.md Building on Lorna's work, this: - changes housekeeping to governance to avoid conflict with the issue label - tightens up the instructions (wordsmithing and general cleanup) - re-orders meeting info and CoC - shortens the ideal time for the first two items to 5 mins --------- Co-authored-by: Marsh Gardiner <[email protected]>
Signed-off-by: Vincent Biret <[email protected]>
Signed-off-by: Vincent Biret <[email protected]>
Signed-off-by: Vincent Biret <[email protected]>
moving Uri to emeritus
Signed-off-by: Mike Ralphson <[email protected]> Co-authored-by: Mike Ralphson <[email protected]>
adds missing package lock for reproductible CI
Fix validate script
Checkout package-lock.json from main and use node v20. Add --yes to npx because it seems to need it when run locally, although it's probably redundant in the CI environment. But it's safe to include.
…Specification into clean-guidelines
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 1.2.2 to 1.3.0. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.3.0/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
….3.0 Bump vitest from 1.2.2 to 1.3.0
In yet another attempt to prevent people from opening PRs that we cannot accept.
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 1.3.0 to 1.3.1. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.3.1/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
….3.1 Bump vitest from 1.3.0 to 1.3.1
Clean guidelines
Bumps [yaml](https://github.com/eemeli/yaml) from 2.3.4 to 2.4.0. - [Release notes](https://github.com/eemeli/yaml/releases) - [Commits](eemeli/yaml@v2.3.4...v2.4.0) --- updated-dependencies: - dependency-name: yaml dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Bump yaml from 2.3.4 to 2.4.0
* Added security considerations document * Update SECURITY_CONSIDERATIONS.md Co-authored-by: Asbjørn Ulsberg <[email protected]> * Update SECURITY_CONSIDERATIONS.md Co-authored-by: Asbjørn Ulsberg <[email protected]> * Add note about external references being potentially on untrusted domains * Update SECURITY_CONSIDERATIONS.md Co-authored-by: Ralf Handl <[email protected]> * Update SECURITY_CONSIDERATIONS.md Co-authored-by: Lorna Jane Mitchell <[email protected]> * Added note about security schemes --------- Co-authored-by: Asbjørn Ulsberg <[email protected]> Co-authored-by: Ralf Handl <[email protected]> Co-authored-by: Lorna Jane Mitchell <[email protected]>
Add markdown style guide to CONTRIBUTING
EDITORS.md: list of current and former specification editors
build script: example links point to HTML wrapper on learn site
Bumps [@hyperjump/json-schema](https://github.com/hyperjump-io/json-schema) from 1.9.6 to 1.9.8. - [Commits](hyperjump-io/json-schema@v1.9.6...v1.9.8) --- updated-dependencies: - dependency-name: "@hyperjump/json-schema" dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…p/json-schema-1.9.8 Bump @hyperjump/json-schema from 1.9.6 to 1.9.8
Bumps [yaml](https://github.com/eemeli/yaml) from 2.5.0 to 2.5.1. - [Release notes](https://github.com/eemeli/yaml/releases) - [Commits](eemeli/yaml@v2.5.0...v2.5.1) --- updated-dependencies: - dependency-name: yaml dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bump yaml from 2.5.0 to 2.5.1
Why are we merging main into 3.1.1 when we're just about to merge 3.1.1 into main? Apologies if I missed somewhere that documents this. |
Same as 3.0.4: From a DM conversation, apparently this is how it's preferred to resolve conflicts, which seems messy to me but I won't object to it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think all I really care about here is that 3.1.1.md
was not changed, and that looks correct here. 3.1.0.md
being taken from main
is also correct and fixes an annoying problem with branch divergence.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
almost done
This merges current
main
intov3.1.1-dev
, resolving the three merge conflicts in