Repository navigation
chore: prepare 1.0.2-alpha.0 development - #1045
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Tomasz Naumowicz (tnaum-ms)
enabled auto-merge
October 22, 2026 08:52
Vsevolod Kukol (sevoku)
approved these changes
Oct 22, 2026
Contributor
✅ CI passed: standard tier (ready PR)Commit
Full run: add the Code quality
Build sizeNo page, activation, VSIX or other bundle size changed by 5% or 50 KiB or more against Artifacts: VSIX | Bundle-reports-39750074487 | L1-manifest-report-39750074487 All graphs (exact bytes)
Packaged bytes. Shared chunks count in every graph that loads them, so rows do not add up. Updated in place on every run. |
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.
Why this change is needed
Move
mainto the next development version so ongoing development no longer uses an already released version.The published release and its tag are unchanged.
Version change
package.json1.0.11.0.2-alpha.0package-lock.json(both root version entries)1.0.11.0.2-alpha.0alpha.0means the first alpha of the next patch;.0is the prerelease counter.Reruns do not advance it to
alpha.1. Workspace package and dependency versions are unchanged.Nothing is published or merged automatically. Replace the alpha with the intended numeric version before the next release.
Source