| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
ci(e2e): fix docusaurus javascript test (#6417) **What's the problem this PR addresses?** The Docusaurus JavaScript e2e test started failing at 2024-03-29T20:01:12.000Z / https://github.com/yarnpkg/berry/actions/runs/8485023278 due to it prompting for which template to use. **How did you fix it?** Update the command to specify the JavaScript template. **Checklist** - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). - [x] I have set the packages that need to be released for my changes to be effective. - [x] I will check that all automated PR checks pass before the PR gets reviewed. | 2 年前 | |
E2E: Fix most E2E tests (#7228) <!-- IMPORTANT: While Yarn 4.x is still actively developed we're now focusing work on our next major releases (5.x and 6.x). These sister releases use the same pattern as TypeScript-Go: - 5.x will only contain a handful of breaking changes to provide a safe migration path. - 6.x will be the "true" release, notable for being implemented in Rust and including a significantly improved core. While PRs can still be opened against 4.x, we recommend power users to try Yarn 6.x now and help us get it over the finish line. It uses the same testsuite as Berry, so compatibility should be at its best. To check out the working trunk for Yarn 6.x, please refer to this repository: https://github.com/yarnpkg/zpm --> ## What's the problem this PR addresses? Many of our E2E tests are failing ## How did you fix it? Some of the tests are failing because they install the latest `typescript`, which currently has no PnP support. These are fixed by limiting the range to `<7.0.0-0` - **Create-Vue**: Added built-in extensions to resolve peer dependency issue - **ESBuild**: Limited `typescript` range - **ESLint**: Limited `typescript` range - **Gatsby**: Unplugged `gatsby`. See https://github.com/gatsbyjs/gatsby/pull/39616 - **Next**: Bypassed the default time gate (the test is against `canary`) - **Parcel**: Added built-in extensions to resolve peer dependency issue - **Angular (PnP)**: Unpinned the node version used in the test from v20 - **SvelteKit**: Migrate away from deprecated `create-svelte` CLI - **TypeScript**: Limited `typescript` range - **WebPack**: Limited `typescript` range Also fixed a few [UUOC](https://en.wikipedia.org/w/index.php?title=Cat_(Unix)&oldid=1362918950#Useless_use_of_cat) Didn't fix the Husky and Storybook tests, as those seem to require code changes on their side. The TypeScript test isn't fully fixed either; looks like it was already broken before 7.0 when TS 6.0 made breaking default config changes. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Co-authored-by: Maël Nison <nison.mael@gmail.com> | 3 个月前 | |
E2E: Fix most E2E tests (#7228) <!-- IMPORTANT: While Yarn 4.x is still actively developed we're now focusing work on our next major releases (5.x and 6.x). These sister releases use the same pattern as TypeScript-Go: - 5.x will only contain a handful of breaking changes to provide a safe migration path. - 6.x will be the "true" release, notable for being implemented in Rust and including a significantly improved core. While PRs can still be opened against 4.x, we recommend power users to try Yarn 6.x now and help us get it over the finish line. It uses the same testsuite as Berry, so compatibility should be at its best. To check out the working trunk for Yarn 6.x, please refer to this repository: https://github.com/yarnpkg/zpm --> ## What's the problem this PR addresses? Many of our E2E tests are failing ## How did you fix it? Some of the tests are failing because they install the latest `typescript`, which currently has no PnP support. These are fixed by limiting the range to `<7.0.0-0` - **Create-Vue**: Added built-in extensions to resolve peer dependency issue - **ESBuild**: Limited `typescript` range - **ESLint**: Limited `typescript` range - **Gatsby**: Unplugged `gatsby`. See https://github.com/gatsbyjs/gatsby/pull/39616 - **Next**: Bypassed the default time gate (the test is against `canary`) - **Parcel**: Added built-in extensions to resolve peer dependency issue - **Angular (PnP)**: Unpinned the node version used in the test from v20 - **SvelteKit**: Migrate away from deprecated `create-svelte` CLI - **TypeScript**: Limited `typescript` range - **WebPack**: Limited `typescript` range Also fixed a few [UUOC](https://en.wikipedia.org/w/index.php?title=Cat_(Unix)&oldid=1362918950#Useless_use_of_cat) Didn't fix the Husky and Storybook tests, as those seem to require code changes on their side. The TypeScript test isn't fully fixed either; looks like it was already broken before 7.0 when TS 6.0 made breaking default config changes. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Co-authored-by: Maël Nison <nison.mael@gmail.com> | 3 个月前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
E2E: Fix most E2E tests (#7228) <!-- IMPORTANT: While Yarn 4.x is still actively developed we're now focusing work on our next major releases (5.x and 6.x). These sister releases use the same pattern as TypeScript-Go: - 5.x will only contain a handful of breaking changes to provide a safe migration path. - 6.x will be the "true" release, notable for being implemented in Rust and including a significantly improved core. While PRs can still be opened against 4.x, we recommend power users to try Yarn 6.x now and help us get it over the finish line. It uses the same testsuite as Berry, so compatibility should be at its best. To check out the working trunk for Yarn 6.x, please refer to this repository: https://github.com/yarnpkg/zpm --> ## What's the problem this PR addresses? Many of our E2E tests are failing ## How did you fix it? Some of the tests are failing because they install the latest `typescript`, which currently has no PnP support. These are fixed by limiting the range to `<7.0.0-0` - **Create-Vue**: Added built-in extensions to resolve peer dependency issue - **ESBuild**: Limited `typescript` range - **ESLint**: Limited `typescript` range - **Gatsby**: Unplugged `gatsby`. See https://github.com/gatsbyjs/gatsby/pull/39616 - **Next**: Bypassed the default time gate (the test is against `canary`) - **Parcel**: Added built-in extensions to resolve peer dependency issue - **Angular (PnP)**: Unpinned the node version used in the test from v20 - **SvelteKit**: Migrate away from deprecated `create-svelte` CLI - **TypeScript**: Limited `typescript` range - **WebPack**: Limited `typescript` range Also fixed a few [UUOC](https://en.wikipedia.org/w/index.php?title=Cat_(Unix)&oldid=1362918950#Useless_use_of_cat) Didn't fix the Husky and Storybook tests, as those seem to require code changes on their side. The TypeScript test isn't fully fixed either; looks like it was already broken before 7.0 when TS 6.0 made breaking default config changes. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Co-authored-by: Maël Nison <nison.mael@gmail.com> | 3 个月前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
E2E: Fix most E2E tests (#7228) <!-- IMPORTANT: While Yarn 4.x is still actively developed we're now focusing work on our next major releases (5.x and 6.x). These sister releases use the same pattern as TypeScript-Go: - 5.x will only contain a handful of breaking changes to provide a safe migration path. - 6.x will be the "true" release, notable for being implemented in Rust and including a significantly improved core. While PRs can still be opened against 4.x, we recommend power users to try Yarn 6.x now and help us get it over the finish line. It uses the same testsuite as Berry, so compatibility should be at its best. To check out the working trunk for Yarn 6.x, please refer to this repository: https://github.com/yarnpkg/zpm --> ## What's the problem this PR addresses? Many of our E2E tests are failing ## How did you fix it? Some of the tests are failing because they install the latest `typescript`, which currently has no PnP support. These are fixed by limiting the range to `<7.0.0-0` - **Create-Vue**: Added built-in extensions to resolve peer dependency issue - **ESBuild**: Limited `typescript` range - **ESLint**: Limited `typescript` range - **Gatsby**: Unplugged `gatsby`. See https://github.com/gatsbyjs/gatsby/pull/39616 - **Next**: Bypassed the default time gate (the test is against `canary`) - **Parcel**: Added built-in extensions to resolve peer dependency issue - **Angular (PnP)**: Unpinned the node version used in the test from v20 - **SvelteKit**: Migrate away from deprecated `create-svelte` CLI - **TypeScript**: Limited `typescript` range - **WebPack**: Limited `typescript` range Also fixed a few [UUOC](https://en.wikipedia.org/w/index.php?title=Cat_(Unix)&oldid=1362918950#Useless_use_of_cat) Didn't fix the Husky and Storybook tests, as those seem to require code changes on their side. The TypeScript test isn't fully fixed either; looks like it was already broken before 7.0 when TS 6.0 made breaking default config changes. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Co-authored-by: Maël Nison <nison.mael@gmail.com> | 3 个月前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
E2E: Fix most E2E tests (#7228) <!-- IMPORTANT: While Yarn 4.x is still actively developed we're now focusing work on our next major releases (5.x and 6.x). These sister releases use the same pattern as TypeScript-Go: - 5.x will only contain a handful of breaking changes to provide a safe migration path. - 6.x will be the "true" release, notable for being implemented in Rust and including a significantly improved core. While PRs can still be opened against 4.x, we recommend power users to try Yarn 6.x now and help us get it over the finish line. It uses the same testsuite as Berry, so compatibility should be at its best. To check out the working trunk for Yarn 6.x, please refer to this repository: https://github.com/yarnpkg/zpm --> ## What's the problem this PR addresses? Many of our E2E tests are failing ## How did you fix it? Some of the tests are failing because they install the latest `typescript`, which currently has no PnP support. These are fixed by limiting the range to `<7.0.0-0` - **Create-Vue**: Added built-in extensions to resolve peer dependency issue - **ESBuild**: Limited `typescript` range - **ESLint**: Limited `typescript` range - **Gatsby**: Unplugged `gatsby`. See https://github.com/gatsbyjs/gatsby/pull/39616 - **Next**: Bypassed the default time gate (the test is against `canary`) - **Parcel**: Added built-in extensions to resolve peer dependency issue - **Angular (PnP)**: Unpinned the node version used in the test from v20 - **SvelteKit**: Migrate away from deprecated `create-svelte` CLI - **TypeScript**: Limited `typescript` range - **WebPack**: Limited `typescript` range Also fixed a few [UUOC](https://en.wikipedia.org/w/index.php?title=Cat_(Unix)&oldid=1362918950#Useless_use_of_cat) Didn't fix the Husky and Storybook tests, as those seem to require code changes on their side. The TypeScript test isn't fully fixed either; looks like it was already broken before 7.0 when TS 6.0 made breaking default config changes. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Co-authored-by: Maël Nison <nison.mael@gmail.com> | 3 个月前 | |
E2E: Fix most E2E tests (#7228) <!-- IMPORTANT: While Yarn 4.x is still actively developed we're now focusing work on our next major releases (5.x and 6.x). These sister releases use the same pattern as TypeScript-Go: - 5.x will only contain a handful of breaking changes to provide a safe migration path. - 6.x will be the "true" release, notable for being implemented in Rust and including a significantly improved core. While PRs can still be opened against 4.x, we recommend power users to try Yarn 6.x now and help us get it over the finish line. It uses the same testsuite as Berry, so compatibility should be at its best. To check out the working trunk for Yarn 6.x, please refer to this repository: https://github.com/yarnpkg/zpm --> ## What's the problem this PR addresses? Many of our E2E tests are failing ## How did you fix it? Some of the tests are failing because they install the latest `typescript`, which currently has no PnP support. These are fixed by limiting the range to `<7.0.0-0` - **Create-Vue**: Added built-in extensions to resolve peer dependency issue - **ESBuild**: Limited `typescript` range - **ESLint**: Limited `typescript` range - **Gatsby**: Unplugged `gatsby`. See https://github.com/gatsbyjs/gatsby/pull/39616 - **Next**: Bypassed the default time gate (the test is against `canary`) - **Parcel**: Added built-in extensions to resolve peer dependency issue - **Angular (PnP)**: Unpinned the node version used in the test from v20 - **SvelteKit**: Migrate away from deprecated `create-svelte` CLI - **TypeScript**: Limited `typescript` range - **WebPack**: Limited `typescript` range Also fixed a few [UUOC](https://en.wikipedia.org/w/index.php?title=Cat_(Unix)&oldid=1362918950#Useless_use_of_cat) Didn't fix the Husky and Storybook tests, as those seem to require code changes on their side. The TypeScript test isn't fully fixed either; looks like it was already broken before 7.0 when TS 6.0 made breaking default config changes. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Co-authored-by: Maël Nison <nison.mael@gmail.com> | 3 个月前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
ci: use react with vite in storybook E2E (#6864) ## What's the problem this PR addresses? - closes https://github.com/yarnpkg/berry/issues/6696 The workflow [.github/workflows/e2e-storybook-workflow.yml](https://github.com/yarnpkg/berry/blob/master/.github/workflows/e2e-storybook-workflow.yml) fails with ```text create-react-app is deprecated. You can find a list of up-to-date React frameworks on react.dev For more info see:https://react.dev/link/cra This error message will only be shown once per install. /tmp/xfs-1a340a15/dlx-2010/.pnp.cjs:5738 throw EROFS(`open '${p}'`); ``` It was last successful on Dec 28, 2024. ## How did you fix it? In the workflow [.github/workflows/e2e-storybook-workflow.yml](https://github.com/yarnpkg/berry/blob/master/.github/workflows/e2e-storybook-workflow.yml) replace ```yaml yarn create react-app my-cra && cd my-cra ``` using ```yaml yarn create vite react --template react && cd react ``` ## Checklist - [X] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). - [X] I have set the packages that need to be released for my changes to be effective. - [X] I will check that all automated PR checks pass before the PR gets reviewed. | 1 年前 | |
E2E: Fix most E2E tests (#7228) <!-- IMPORTANT: While Yarn 4.x is still actively developed we're now focusing work on our next major releases (5.x and 6.x). These sister releases use the same pattern as TypeScript-Go: - 5.x will only contain a handful of breaking changes to provide a safe migration path. - 6.x will be the "true" release, notable for being implemented in Rust and including a significantly improved core. While PRs can still be opened against 4.x, we recommend power users to try Yarn 6.x now and help us get it over the finish line. It uses the same testsuite as Berry, so compatibility should be at its best. To check out the working trunk for Yarn 6.x, please refer to this repository: https://github.com/yarnpkg/zpm --> ## What's the problem this PR addresses? Many of our E2E tests are failing ## How did you fix it? Some of the tests are failing because they install the latest `typescript`, which currently has no PnP support. These are fixed by limiting the range to `<7.0.0-0` - **Create-Vue**: Added built-in extensions to resolve peer dependency issue - **ESBuild**: Limited `typescript` range - **ESLint**: Limited `typescript` range - **Gatsby**: Unplugged `gatsby`. See https://github.com/gatsbyjs/gatsby/pull/39616 - **Next**: Bypassed the default time gate (the test is against `canary`) - **Parcel**: Added built-in extensions to resolve peer dependency issue - **Angular (PnP)**: Unpinned the node version used in the test from v20 - **SvelteKit**: Migrate away from deprecated `create-svelte` CLI - **TypeScript**: Limited `typescript` range - **WebPack**: Limited `typescript` range Also fixed a few [UUOC](https://en.wikipedia.org/w/index.php?title=Cat_(Unix)&oldid=1362918950#Useless_use_of_cat) Didn't fix the Husky and Storybook tests, as those seem to require code changes on their side. The TypeScript test isn't fully fixed either; looks like it was already broken before 7.0 when TS 6.0 made breaking default config changes. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Co-authored-by: Maël Nison <nison.mael@gmail.com> | 3 个月前 | |
E2E: Fix most E2E tests (#7228) <!-- IMPORTANT: While Yarn 4.x is still actively developed we're now focusing work on our next major releases (5.x and 6.x). These sister releases use the same pattern as TypeScript-Go: - 5.x will only contain a handful of breaking changes to provide a safe migration path. - 6.x will be the "true" release, notable for being implemented in Rust and including a significantly improved core. While PRs can still be opened against 4.x, we recommend power users to try Yarn 6.x now and help us get it over the finish line. It uses the same testsuite as Berry, so compatibility should be at its best. To check out the working trunk for Yarn 6.x, please refer to this repository: https://github.com/yarnpkg/zpm --> ## What's the problem this PR addresses? Many of our E2E tests are failing ## How did you fix it? Some of the tests are failing because they install the latest `typescript`, which currently has no PnP support. These are fixed by limiting the range to `<7.0.0-0` - **Create-Vue**: Added built-in extensions to resolve peer dependency issue - **ESBuild**: Limited `typescript` range - **ESLint**: Limited `typescript` range - **Gatsby**: Unplugged `gatsby`. See https://github.com/gatsbyjs/gatsby/pull/39616 - **Next**: Bypassed the default time gate (the test is against `canary`) - **Parcel**: Added built-in extensions to resolve peer dependency issue - **Angular (PnP)**: Unpinned the node version used in the test from v20 - **SvelteKit**: Migrate away from deprecated `create-svelte` CLI - **TypeScript**: Limited `typescript` range - **WebPack**: Limited `typescript` range Also fixed a few [UUOC](https://en.wikipedia.org/w/index.php?title=Cat_(Unix)&oldid=1362918950#Useless_use_of_cat) Didn't fix the Husky and Storybook tests, as those seem to require code changes on their side. The TypeScript test isn't fully fixed either; looks like it was already broken before 7.0 when TS 6.0 made breaking default config changes. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Co-authored-by: Maël Nison <nison.mael@gmail.com> | 3 个月前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
E2E: Fix most E2E tests (#7228) <!-- IMPORTANT: While Yarn 4.x is still actively developed we're now focusing work on our next major releases (5.x and 6.x). These sister releases use the same pattern as TypeScript-Go: - 5.x will only contain a handful of breaking changes to provide a safe migration path. - 6.x will be the "true" release, notable for being implemented in Rust and including a significantly improved core. While PRs can still be opened against 4.x, we recommend power users to try Yarn 6.x now and help us get it over the finish line. It uses the same testsuite as Berry, so compatibility should be at its best. To check out the working trunk for Yarn 6.x, please refer to this repository: https://github.com/yarnpkg/zpm --> ## What's the problem this PR addresses? Many of our E2E tests are failing ## How did you fix it? Some of the tests are failing because they install the latest `typescript`, which currently has no PnP support. These are fixed by limiting the range to `<7.0.0-0` - **Create-Vue**: Added built-in extensions to resolve peer dependency issue - **ESBuild**: Limited `typescript` range - **ESLint**: Limited `typescript` range - **Gatsby**: Unplugged `gatsby`. See https://github.com/gatsbyjs/gatsby/pull/39616 - **Next**: Bypassed the default time gate (the test is against `canary`) - **Parcel**: Added built-in extensions to resolve peer dependency issue - **Angular (PnP)**: Unpinned the node version used in the test from v20 - **SvelteKit**: Migrate away from deprecated `create-svelte` CLI - **TypeScript**: Limited `typescript` range - **WebPack**: Limited `typescript` range Also fixed a few [UUOC](https://en.wikipedia.org/w/index.php?title=Cat_(Unix)&oldid=1362918950#Useless_use_of_cat) Didn't fix the Husky and Storybook tests, as those seem to require code changes on their side. The TypeScript test isn't fully fixed either; looks like it was already broken before 7.0 when TS 6.0 made breaking default config changes. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Co-authored-by: Maël Nison <nison.mael@gmail.com> | 3 个月前 | |
CI: Do not require tests using nightly Node.js version to pass (#7287) ## What's the problem this PR addresses? The CI integration tests are failing on nightly Node.js releases When I wrote #7224, the nightly tests were part of the required checks on PRs. So I included them in the aggregate results check. ## How did you fix it? Add `continue-on-error` to integrations tests on nightly versions. This prevents them from showing as failure in PR checks but keeps the visibility of whether we are compatible with future Node.js versions. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. | 7 天前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
ci: properly mint a provenance token in release workflows (#6754) ## What's the problem this PR addresses? Follow-up #6750: enable provenance statements for Yarn ## How did you fix it? <!-- A detailed description of your implementation. --> Added `permissions: id-token: write` to publication workflows ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. | 1 年前 | |
ci: properly mint a provenance token in release workflows (#6754) ## What's the problem this PR addresses? Follow-up #6750: enable provenance statements for Yarn ## How did you fix it? <!-- A detailed description of your implementation. --> Added `permissions: id-token: write` to publication workflows ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. | 1 年前 | |
Update release-rerun.yml | 4 个月前 | |
chore: Update GitHub actions versions (#6279) Saw a bunch of warnings while checking a log, apparently these versions use node 16 which is deprecated, and the v3 of upload-artifact and download-artifact will stop working in November. | 2 年前 | |
ci: disable stale bot (#5122) | 3 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 3 个月前 | ||
| 3 个月前 | ||
| 2 年前 | ||
| 3 个月前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 3 个月前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 3 个月前 | ||
| 3 个月前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 3 个月前 | ||
| 3 个月前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 3 个月前 | ||
| 7 天前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 4 个月前 | ||
| 2 年前 | ||
| 3 年前 |