Repository navigation
deps: Bump vitest from 3.2.4 to 4.1.2 - #11
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.4 to 4.1.2. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.2/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.2
branch
from
April 2, 2026 09:49
38f7ecb to
b0626fb
Compare
Author
|
Superseded by #27. |
AlbSar
pushed a commit
that referenced
this pull request
May 6, 2026
… 2 timeline revised End-of-day ROADMAP sync. Reflects every Sprint 153 commit landed today (224618c → 2f7f7d8, 14 commits) and resets the doc as the canonical hand-off for tomorrow's Sprint 154 kickoff. Updates: - Header `Last update:` 2026-05-06 evening + `Next audit:` Sprint 154 start (was: Sprint 153 finalize sonrası) - "Sprint 153 Kalan İş" section retitled "Sprint 153 — Gerçekleşen İş (TÜMÜ ✅)" with every line item moved to a checkmark and a one-line outcome each (CI greening, Vitepress, orphan-cleaner, archive-debt, Node 18 purge, D1-D4, Coverage flake guard, docker timeout clarity, B1+B2 Nervous wire, B3 end-to-end test, E Ed25519 + 20 seed sign + install verify, run-param, local 0-byte bin fix). Hub public key recorded. - New "Sprint 154 — Yarına Devam Eden İş" section: A1+A2 Telegram/Discord smoke (Pazar token), Sprint 153 retro Brain output, B3 production detector log evidence, deckent_run timeout-cap audit re-run with the new effort=high override, optional Phase 2 calendar revision. - Phase 2 master roadmap (Section 4) — replaced the slipped 23-Apr/24-Apr Community-Bug-Triage / WhatsApp-Business plan with what actually shipped (152 audit, 152.5 HF day, 153 CI greening + Node 20 + B + E + run-param). Sprint 154-161 dates pushed forward proportionally. - Section 5 Beta GA Exit Criteria header `17/20` → `19/20`. Gate #11 (doc sync) flipped 🟡→✅. Gate #15 (hub publish + sign) flipped 🟡→✅ with Sprint 153 E credit. Gate #13 (messaging) annotated "token Pazar bekleniyor, kod hazır." Closing line rewritten — only #13 remains (excluding long-term #3 coverage). Implicit "CI Workflow Health" gate added explicitly. - Section 11 Anchor Kuralları — three new rules: 13. Node.js >=20 minimum (CI matrix [20.x,22.x,24.x], better-sqlite3 + vite already require it, .npmrc ignore-scripts pattern with node-gyp rebuild step) 14. CI-green-before-push imperative + the 0-byte .bin/ zombie gotcha + direct-invoke fallbacks (`node node_modules/typescript/bin/tsc`) 15. Beta GA Gate #15 closure note + project hub key value Meta-dogfood counter (rule 12) extended through Sprint 153 (4 new evidences). - Closing signatures: 2026-05-06 entry added. This single doc update is intentionally not bundled with code changes so the diff stays purely narrative. Tomorrow's first read is this file. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps vitest from 3.2.4 to 4.1.2.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
fc6f482chore: release v4.1.26f97b55feat: disable colors if agent is detected (#9851)b3c992cfix(coverage): correctcoverageConfigDefaultsvalues and types (#9940)7c06598fix: ensure sequential mock/unmock resolution (#9830)f54abadchore: add typo-checker skill and fix typos (#9963)7aa9377fix: don't resolvesetupFilesfrom parent directory (#9960)1f2d318chore: release v4.1.1ebfde79refactor: renamematchesTagsFiltertomatchesTags(#9956)5611500feat(experimental): introduceexperimental.vcsProvider(#9928)eec53d9feat(experimental): exposematchesTagsFilterto test if the current filter ...Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vitest since your current version.