-
Notifications
You must be signed in to change notification settings - Fork 1.7k
chore(deps): bump vite from 6.3.5 to 6.3.6 #940
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
Conversation
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.3.5 to 6.3.6. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v6.3.6/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v6.3.6/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 6.3.6 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
✅ Deploy Preview for all-contributors ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
I think we can merge this. I'd love a second opinion @JimMadge on our CI before I do. Notice above, there are three CI checks LINT: checks for linting What I'm noticing is that we don't have an explicit build docs CI label here, so when you go to approve it, it appears that the build docs step didn't happen, but it actually occurs in the offline link check step. Should we rename that workshop to be build docs and check links just to make the CI steps above more expressive? It's a minor suggestion, but I started to think that we needed to run build docs and then realized that may be redundant. I am curious what you think. Alternatively, we could merge the two workflows (build and deploy, and link check) together and put a condition on the deploy step. I might be overthinking this :) |
|
A newer version of vite exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
|
@lwasser I think that is sensible. Can you open an issue. It would be good to do this with one workflow but a number of dependent jobs,
with the built documentation passing between the jobs. |
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.3.5 to 6.3.6. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v6.3.6/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v6.3.6/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 6.3.6 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Leah Wasser <leah@pyopensci.org> Co-authored-by: Jim Madge <jim@jmadge.com>
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.3.5 to 6.3.6. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v6.3.6/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v6.3.6/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 6.3.6 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Leah Wasser <leah@pyopensci.org> Co-authored-by: Jim Madge <jim@jmadge.com>
* docs: add page on pr merge governance * docs: more on squash commiting * docs: fix linting * Apply suggestion from @JimMadge Co-authored-by: Jim Madge <jim+github@jmadge.com> * docs: add a maintainers merge pr guide * chore(deps): bump vite from 6.3.5 to 6.3.6 (#940) Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.3.5 to 6.3.6. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v6.3.6/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v6.3.6/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 6.3.6 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Leah Wasser <leah@pyopensci.org> Co-authored-by: Jim Madge <jim@jmadge.com> * chore: linting --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Jim Madge <jim@jmadge.com> Co-authored-by: Jim Madge <jim+github@jmadge.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps vite from 6.3.5 to 6.3.6.
Release notes
Sourced from vite's releases.
Changelog
Sourced from vite's changelog.
Commits
3f337c5release: v6.3.6e11d240fix: upgrade sirv to 3.0.2 (#20735)0ab19eafix: applyfs.strictcheck to HTML files (#20736)7d99229test: detect ts support viaprocess.features(#20544)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.