Repository navigation
Update bundled BeatBrowser to 1.4.1 - #20
Merged
Merged
Conversation
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.
BeatGEO bundled BeatBrowser 1.3.2 while the current release is 1.4.1. Pin the dependency and lockfile to the exact 1.4.1 release commit and update the third-party notice. Setup now prepares a matching 1.4.1 extension; remote access remains opt-in. No additional account, database or global browser install is introduced.
Validation: pnpm lint and all workspace type checks passed. The MVP regression passed: 1,563 checks across collector/script/unit/integration suites, using synthetic provider responses and disposable bundled PostgreSQL. Restart persistence, transaction rollback, concurrent database connections and duplicate-instance protection passed. Confirmed both installed package and prepared extension report 1.4.1. The full regression ran with the identical 1.4.0 runtime; 1.4.1 changes only version metadata and documentation. Rechecked the final install, extension preparation and lint. No live model session or overnight scheduling verification is claimed.