Release 0.14.0 — integrate beta → main - #181
Merged
Merged
Conversation
Co-authored-by: Simon Heather <simon.heather@yulife.com>
Co-authored-by: Simon Heather <simon.heather@yulife.com>
Co-authored-by: Simon Heather <simon.heather@yulife.com>
eFAILution
changed the title
Contributor
🛡️ Security Hardening Pipeline ResultsBranch: Workflow Run: 254 Scan Status
Summaries Collected: 2 Scanner Results🔬 CodeQL SAST (Javascript)Status: Completed Findings Summary
No security findings detected for Javascript. Artifacts: CodeQL Reports (Javascript) 🔗 Dependency ReviewStatus: ✅ No issues found No vulnerable or license-violating dependencies detected in this PR. Generated by Argus Generated by Argus |
Ignore semver-minor/major version-updates for @types/vscode so it cannot exceed engines.vscode again; only patch bumps within the floor are allowed. A minor/major raise must accompany a deliberate engines bump. Dependabot reads this config from the default branch, so the rule takes effect once it reaches main.
Co-authored-by: Simon Heather <simon.heather@yulife.com>
eFAILution
had a problem deploying
to
publish-beta
June 22, 2026 17:07 — with 
GitHub Actions
Failure
GitHub Actions
Failure
… name returns nothing (#192) Co-authored-by: Simon Heather <simon.heather@yulife.com>
Flags GitLab CI component includes pinned to a semver ref that has a newer stable release available, across three surfaces: - hover shows the latest available version next to the current one - an on-save warning squiggle on the outdated ref, with an "Update to X" quick-fix - a "Update All Component Versions to Latest" command for the active file Only clean X.Y.Z refs (optional v prefix) are eligible; floating, branch, and SHA refs are left untouched and pre-releases are never suggested. Version comparison is in-house (no new dependency). Version lookups reuse the per-project tag cache and run on open/save, in a dedicated diagnostic collection so they never clobber the input/structure diagnostics. New, pure, unit-tested modules: src/utils/semver.ts and src/providers/componentVersionCheck.ts. Wired into ValidationProvider, HoverProvider, package.json contributions, and a new command. Closes #193 Co-authored-by: eFAILution <eFAILution@users.noreply.github.com>
…195) Component URLs that use variables (e.g. `$CI_SERVER_FQDN/group/comp@1.2.3`) were passed raw into the version lookup, where URL parsing threw — so no outdated-version squiggle appeared and "Update All Component Versions to Latest" silently skipped them. computeOutdatedRefs now expands variables via the file's repo context (the same getWorkspaceContext + expandComponentUrl path validate() already uses) before fetching versions. The version map stays keyed by the raw base URL — only the lookup uses the expanded URL — so diagnostic ranges, the quick-fix, and the bulk command still land on the document text. Bases whose instance can't be resolved, or that expand incompletely, are left unchecked rather than guessed at. Refs #193 Co-authored-by: eFAILution <eFAILution@users.noreply.github.com>
* docs(readme): refresh stale content and document version-check - Document the version-check feature: hover "Latest" line, outdated-pin squiggle + quick-fix, "Update All Component Versions to Latest" command, semver-only scope, on-save cadence, and variable resolution - Add the missing settings to the reference table: additionalFileGlobs, versionCheck.enabled, versionCheck.severity - Expand the Commands list (new update command + Update/Reset Cache) - Fix the example include to use `inputs:` (GitLab) instead of `with:` - Correct dev prerequisites: VS Code 1.120.0 floor, npm (not yarn) - Replace `username/...` placeholders with the real eFAILution repo and extension id Refs #193 * docs(readme): slim the listing and move advanced guides to docs/ Trims the README to a focused Marketplace listing (~430 -> ~200 lines): - de-duplicate settings — one reference table; drop the repeated prose and the thrice-repeated componentSources example - tone down the marketing copy and merge overlapping Quick Start / Features - move the deep, technical sections out to user guides under docs/ (not .ai/, which is for machine-readable AICaC): - docs/discovery.md — discovery tuning for non-spec repos - docs/monorepo-tags.md — tag-per-component monorepo conventions - docs/api.md — intended extension API, flagged not-yet-exposed - link to the guides with absolute URLs so they resolve on the Marketplace (relative links don't), and keep all sections expanded (the Marketplace renderer doesn't honor collapsible <details>) Refs #193 --------- Co-authored-by: eFAILution <eFAILution@users.noreply.github.com>
* fix: Improve expired token user experience * Refine as per review comments --------- Co-authored-by: Simon Heather <simon.heather@yulife.com>
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
2 participants
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.
Target
Next stable: 0.14.0 — the
0.13.xbeta pre-release line promotes to the next even (stable) minor on merge.Per repo convention (
publish-main.ymlguardrail 7), odd minors are beta-only and even minors are stable: pre-releases are cut frombetaas0.13.x, and merging tomaincuts the0.14.xstable line.Status
betais 24 commits ahead ofmain— 13 substantive PRs/fixes + 1 feature + beta release commits. Current pre-release:0.13.10;mainis0.12.2. All merged and validated in the beta pre-release builds. Diffstat: +2397 / −540 across 45 files.What's in this release
✨ Features
X.Y.Z), hover shows the latest available version (✓ up to date/⚠️ update available), an out-of-date pin gets a warning squiggle with an Update toX.Y.ZQuick Fix, and a new GitLab CI: Update All Component Versions to Latest command bumps every outdated pin in a file. Semver-only (floating refs/SHAs left alone, pre-releases never suggested); runs on open/save and reuses the per-project tag cache. New settings:versionCheck.enabled,versionCheck.severity. (feat(version-check): detect outdated component versions (semver upgrade hints) #194, fix(version-check): expand GitLab variables before fetching versions #195 — fixes feat: surface outdated GitLab CI component versions (semver upgrade hints) #193)🐛 Bug Fixes
component-auth-faileddiagnostic with an Update GitLab token Quick Fix instead of spurious per-input "unknown input" warnings, the token prompt distinguishes expired-vs-missing and states the requiredread_apiscope, and open documents revalidate automatically once a new token is saved. Also HTML-escapes the browser error views. (fix: Improve expired token user experience #198 — fixes bug: expired/invalid GitLab token gives a confusing recovery experience #197)fileURI scheme, so the read-only diff source panel (Source Control, "Open Changes", GitLens, PR diffs) no longer carries duplicate squiggles. (fix: validation diagnostics appear on both panels of a diff view #180 — fixes bug: validation diagnostics appear on both panels of a diff view #179)component:/include:line now refreshes diagnostics — the ±5-line proximity heuristic is replaced by a throttled (300ms) full re-validation. (fix: validation diagnostics go stale when editing an input far from its component line #178 — fixes bug: validation diagnostics go stale when editing an input far from its component line #177)vscode-freeincludeMatcherutil with unit tests. (fix: validation diagnostics mis-anchored when one file includes the same component/template twice #176 — fixes bug: validation diagnostics mis-anchored when one file includes the same component/template twice #175)${VAR}GitLab variables are recognised in component URLs. (fix: recognise braced ${VAR} GitLab variables in component URLs #182)@types/vscodepinned to^1.120.0to matchengines.vscode— fixes themainCIrelease-job failure (@types/vscodegreater than the engines floor). (a6c7626)📝 Docs
docs/(discovery.md,monorepo-tags.md,api.md), the version-check feature documented, the settings table completed, and the example include corrected (with:→inputs:). (docs: refresh, slim, and split the README #196)dependabot.yml. (docs(ci): document dev-scope security-alert policy in dependabot.yml #183)🔧 CI
@types/vscodebumps past theengines.vscodefloor. (8b3fda8)Validation
betagreen ontest (22.x)+extension-host; the latest beta build is green.validationProvider.ts(the hot file); each was rebased ontobetabefore merge and re-verified together (the version-check and token-auth diagnostics + quick-fixes coexist).npm run release:main:dry(release-it --dry-run) before merge to confirm the computed 0.14.0 version + changelog onmain.Merge checklist
release-it --dry-runpreviews the expected0.14.0version + changelog onmainbeta(note: feat(parser): add pipeline parser and CLI commands #199 targetsmaindirectly, notbeta— separate review thread)main, head isbeta