Repository navigation
chore: merge master back into develop after 6.1.1 - #342
Merged
Merged
Conversation
feat: support okx wallet ext download
style: format packages/core/src/discovery.ts
Add changesets
chore: update versions
Set minor changesets
chore: update versions
fix: use windowObject instead of window to prevent ssr breaking
Master branch version bump
Change stable release to v4
Master branch version bump
Add Xverse to get-starknet discovery list
Master branch version bump
[codex] Backport npm trusted publishing to master
Supersede the v4 line on master with the v6 codebase. Keeps develop's tree in full; records master as merged so master fast-forwards cleanly.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Promote v6 to master (6.1.0 GA)
Master branch version bump
Brings master (6.1.0 GA, cut from develop at #318) up to date with develop: types-js 0.10.4, Noble/Scure 2.x (drops viem), Bramble wallet, and the Dependabot security fixes (#339). Conflicts were limited to package versions and changelogs: packages keep master's 6.1.0; changelogs keep both branches' entries; private docs package takes develop's 0.0.10. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Develop's changesets were consumed when publishing to `next`, so re-declare them here so master's release publishes 6.1.1 to `latest`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
chore: sync develop into master (release 6.1.1 to latest)
Master branch version bump
3 of 4 tasks
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.
Summary
Brings
developback in line withmasterafter #340 and #341 published 6.1.1 tolatest.developis already an ancestor ofmaster, so the only differences are release bookkeeping:docspackage goes to 0.0.11.There are no source, dependency or lockfile changes. After this,
developandmasterhave identical trees, and the nextdeveloprelease will be numbered from 6.1.x instead of 6.0.x.Notes for merging
master's history indevelop, so the next develop→master promotion doesn't hit these version and changelog conflicts again.developshould publish nothing. There are no changesets, and the 6.1.x versions are already on npm. Before merging, check thatnpm view @starknet-io/get-starknet-discovery@6.1.1resolves. Otherwisepublish:nextcould try to republish a version npm is still processing.nextdist-tag will still point at 6.0.x, which is belowlatest, until develop's next release. To fix it sooner, a maintainer can runnpm dist-tag add <pkg>@6.1.1 next(or@6.1.0for core, modal and ui).Test plan
masterat 8961ea8, where the release workflow's build and test passed (run)developis limited to version fields and changelogs (16 files)🤖 Generated with Claude Code