fix: repair corrupted bun.lock breaking CI frozen-lockfile installs#48
Merged
JosunLP merged 3 commits intoJosunLP-patch-1from Mar 12, 2026
Merged
fix: repair corrupted bun.lock breaking CI frozen-lockfile installs#48JosunLP merged 3 commits intoJosunLP-patch-1from
JosunLP merged 3 commits intoJosunLP-patch-1from
Conversation
Merged
…rif from package.json to fix CI Co-authored-by: JosunLP <20913954+JosunLP@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add improvements to documentation and workflow for bQuery.js
fix: repair corrupted bun.lock breaking CI frozen-lockfile installs
Mar 12, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes CI failures caused by a corrupted bun.lock by removing an invalid/dangling dependency entry and shifting the ESLint SARIF formatter install to the ESLint GitHub Actions workflow.
Changes:
- Remove
@microsoft/eslint-formatter-sariffromdevDependenciesinpackage.json. - Remove the dangling
@microsoft/eslint-formatter-sarifworkspace entry frombun.lockto restore lockfile validity. - Update the ESLint workflow to install the SARIF formatter during CI before running ESLint.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Removes SARIF formatter from repo devDependencies to avoid lockfile corruption/unused dependency in normal installs. |
| bun.lock | Deletes the invalid workspace dependency entry that broke bun install --frozen-lockfile. |
| .github/workflows/eslint.yml | Installs SARIF formatter in the CI job so ESLint can output SARIF without bundling it into the repo dependencies. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Jonas Pfalzgraf <jolun.swtor@gmail.com>
JosunLP
added a commit
that referenced
this pull request
Mar 12, 2026
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Co-authored-by: JosunLP <20913954+JosunLP@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Jonas Pfalzgraf <info@josunlp.de> Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Fix PR review issues: duplicate keys, cleanup leaks, export conflicts, and SSR safety (#17) Fix security, type safety, and API surface issues from PR #16 review (#18) Fix router cancellation, component example, and ref directive expression handling (#19) Fix router compatibility, isDev default, style cleanup, and changelog format (#20) Fix hash routing bugs and add comprehensive test coverage (#21) Fix router base path handling, bq-if DOM stability, and CHANGELOG consistency (#22) Fix defineComponent tests, store reactivity leak, view directive signal handling, and hash-routing interception (#24) Fix async handling, type safety, environment guards, and add test coverage from PR #16 review (#25) Fix DOM order reversal, stale dependency tracking, localStorage SafariError, and reactive bq-for updates (#26) Fix view template root validation, store optimizations, and utils API cleanup (#27) Fix bq-show display restoration and timeline.seek() time calculation (#28) Fix router base path duplication and add SSR guards for Element checks (#29) Fix interceptLinks() browser behavior and createTemplate() validation (#30) Fix bq-class bracket detection, once() failure caching, mount bq-for validation, and component pre-mount renders (#31) Fix bq-style whitespace handling and spring variable frame rate (#32) Fix bq-on method reference context loss and remove style attribute from security defaults (#33) Fix persistedSignal localStorage test key collision (#34) Fix bq-class directive stale class cleanup for object syntax (#35) Fix timeline() to account for animation iterations in duration calculations (#36) fix: Reactive robustness, security hardening, storage compat, expression parsing (#37) Fix css() getter, add Signal.dispose(), debounce/throttle cancel, collection.find(), element.is() (#39) fix(ci): align ESLint workflow with repo CI conventions (#47) fix: repair corrupted bun.lock breaking CI frozen-lockfile installs (#48) Fix ESLint workflow failure caused by SARIF formatter runtime mismatch (#50)
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.
@microsoft/eslint-formatter-sarifwas manually added tobun.lock's workspacedevDependenciessection without a resolved entry in thepackagessection, making the lockfile unparseable. This caused every workflow usingbun install --frozen-lockfileto fail:Changes
bun.lock— Remove the dangling@microsoft/eslint-formatter-sarifworkspace entry that had no corresponding package resolutionpackage.json— Remove@microsoft/eslint-formatter-sariffromdevDependencies; it's only consumed by the ESLint workflow, not the broader project.github/workflows/eslint.yml— Install the SARIF formatter as a dedicated step afterbun install --frozen-lockfile, leveraging CI network access rather than baking it into the lockfile📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.