Mike McCready

@PeterDaveHello If you rebase your branch on `main` (or merge `main` into your branch), you should find that the `markdown-link-check` errors are now suppressed. PR #2296 is now merged.

@jennifer-shehane > Yes, we've seen this issue becoming a problem for our users (and some of our own team). Thank you for documenting. There were several users in Discord reporting...

Related: - https://github.com/actions/upload-artifact/pull/719 - https://github.com/actions/download-artifact/pull/434

GitHub released updates on Dec 12, 2025 with `runs.using: node24`: - [actions/[email protected]](https://github.com/actions/upload-artifact/releases/tag/v6.0.0) - [actions/[email protected]](https://github.com/actions/download-artifact/releases/tag/v7.0.0) meaning that this issue can now be progressed.

@jennifer-shehane Does this mean that you are now considering supporting Bun? - As package manager alternative? - As Node.js alternative? - Or both? There are a couple of related issues...

Preview - https://github.com/MikeMcC399/cypress-documentation/blob/ci-docker-aws-codebuild/docs/guides/continuous-integration/aws-codebuild.mdx#testing-with-cypress-docker-images

@KevinPusateri > Any workaround? A workaround to avoid the error message is to disable videos (see https://docs.cypress.io/guides/references/configuration#Videos). Hopefully the label https://github.com/cypress-io/cypress/labels/stage%3A%20backlog on this issue means that it will soon be...

@babyitachi > can I take this one? The Cypress.io team, who are the maintainers, would need to answer your question. I don't know what they are planning at the moment.

@RahulGautamSingh Your experience corresponds to the [README](https://github.com/nodejs/corepack/blob/main/README.md#corepack-use-nameversion) documentation which says: --- ### `corepack use ` When run, this command will retrieve the latest release matching the provided descriptor, assign it...

@JoshuaKGoldberg > * Automatically removing them when in `--fix` mode Currently in `[email protected]`, `npx eslint --fix` does not remove an `eslint-env` comment. That would be nice to have, however I...