Skip to content

Merge develop into main without a new release - #7

Closed
chaiwithcode wants to merge 5 commits into
mainfrom
develop
Closed

chaiwithcode wants to merge 5 commits into
mainfrom
develop

Conversation

@chaiwithcode

Copy link
Copy Markdown
Owner

Bring the approved documentation, Xcode demo project and screenshots, Marketplace badge fixes, and Open VSX submission preparation from develop to main. This aligns main with the existing 1.4.2 code and release; it does not create a new version, tag, GitHub release, or Marketplace publication.\n\nValidation: develop PRs #5 and #6 passed CI. This PR must pass the required Test & Build check before merge.

* fix: replace retired Marketplace badges

* fix: exclude build outputs from VSIX
* Fix retired Marketplace badges (#1)

* fix: replace retired Marketplace badges

* fix: exclude build outputs from VSIX

* Release XBridge 1.4.2 (#3)

* Fix retired Marketplace badges (#1) (#2)

* fix: replace retired Marketplace badges

* fix: exclude build outputs from VSIX

* chore: prepare XBridge 1.4.2 release
* Fix retired Marketplace badges (#1)

* fix: replace retired Marketplace badges

* fix: exclude build outputs from VSIX

* Release XBridge 1.4.2 (#3)

* Fix retired Marketplace badges (#1) (#2)

* fix: replace retired Marketplace badges

* fix: exclude build outputs from VSIX

* chore: prepare XBridge 1.4.2 release
@chaiwithcode

Copy link
Copy Markdown
Owner Author

Superseded by a PR from the conflict-resolved develop tree; GitHub does not permit merge commits for the required history sync.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant