Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 26, 2025

Bumps vite from 6.3.5 to 6.3.6.

Release notes

Sourced from vite's releases.

v6.3.6

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

6.3.6 (2025-09-08)

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will 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.

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>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 26, 2025
@netlify
Copy link

netlify bot commented Sep 26, 2025

Deploy Preview for all-contributors ready!

Name Link
🔨 Latest commit bfd7bac
🔍 Latest deploy log https://app.netlify.com/projects/all-contributors/deploys/68f7595258215a0008a4860c
😎 Deploy Preview https://deploy-preview-940--all-contributors.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@lwasser
Copy link
Member

lwasser commented Oct 8, 2025

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
OFFLINE links: is what you just created. It builds the docs and runs link check
WIP: I believe it is an APP that looks for WIP in the title of the PR. We might be able to remove that, given there are draft pr's now? But I may be missing something.

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.
Part 1 would be building documentation, running Lychee.
Part 2 would be deploy with a conditional:
if branch == main, deploy

I might be overthinking this :)

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 21, 2025

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.

@JimMadge
Copy link
Member

@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,

  • build docs (required for merge)
  • offline link check, depends on build docs (required for merge)
  • deploy, depends on build docs, only when event is push to main

with the built documentation passing between the jobs.

@JimMadge JimMadge merged commit f4468ac into main Oct 21, 2025
7 checks passed
@JimMadge JimMadge deleted the dependabot/npm_and_yarn/vite-6.3.6 branch October 21, 2025 10:00
lwasser added a commit to lwasser/all-contributors that referenced this pull request Nov 1, 2025
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>
lwasser added a commit to lwasser/all-contributors that referenced this pull request Nov 4, 2025
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>
lwasser added a commit that referenced this pull request Nov 12, 2025
* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants