Skip to content

Release 0.16.0 — integrate beta → main - #208

Merged
eFAILution merged 18 commits into
mainfrom
beta
Jul 8, 2026
Merged

eFAILution merged 18 commits into
mainfrom
beta

Conversation

@eFAILution

@eFAILution eFAILution commented Jun 30, 2026

Copy link
Copy Markdown
Owner

Target

Next stable: 0.16.0 — the 0.15.x beta pre-release line promotes to the next even (stable) minor on merge. Per repo convention (publish-main.yml guardrail 7 / docs/RELEASING.md): odd minors are beta-only, even minors are stable.

Status

beta is 10 substantive commits ahead of main (plus the 0.15.00.15.6 release bumps). main is 0.14.5; merging cuts 0.16.0. Integrated beta build is green (lint + 329 unit tests + extension-host).

What's in this release

✨ Features

🐛 Bug Fixes

🧹 Chores · CI · Docs

🧪 Tests

Validation

  • Each beta PR was green on test (22.x) + extension-host. Integrated beta re-verified: lint + 329 unit tests + extension-host green.
  • Recommend a final npm run release:main:dry before merge to confirm the computed 0.16.0 version + changelog on main.

Merge checklist

X-Guardian and others added 4 commits June 29, 2026 21:41
…lt never shows its dropdown (#205)

Co-authored-by: Simon Heather <simon.heather@yulife.com>
…ncludes (#207)

* fix: no input suggestions for the second of two identical component includes

* Add extension-host tests

---------

Co-authored-by: Simon Heather <simon.heather@yulife.com>
…#207 integration

#205 added a `slot` discriminator to the context returned by
findCompletionInputContextAtLine; #207's duplicate-include test (merged after)
asserted the pre-slot shape, so it failed once both landed on beta together.
Add `slot: 'name'` to the expectation.
@github-actions

github-actions Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

🛡️ Security Hardening Pipeline Results

Branch: beta
Commit: 18308f9

Workflow Run: 304
Branch: beta
Commit: 18308f9

Scan Status

Scanner Status
bandit ⏭️ skipped
checkov ⏭️ skipped
clamav ⏭️ skipped
codeql ✅ PASS
container ⏭️ skipped
dependency-review ✅ PASS
gitleaks ✅ PASS
grype ⏭️ skipped
infrastructure ⏭️ skipped
lint ⏭️ skipped
opengrep ⏭️ skipped
osv ✅ PASS
sbom ⏭️ skipped
supply-chain ⏭️ skipped
trivy-container ⏭️ skipped
trivy-iac ⏭️ skipped
zap ⏭️ skipped

✅ All enabled scanners completed successfully.

Summaries Collected: 2

Scanner Results

🔬 CodeQL SAST (Javascript)

Status: Completed

Findings Summary

Critical High Medium Low Total
0 0 0 0 0

No security findings detected for Javascript.

Artifacts: CodeQL Reports (Javascript)

🔗 Dependency Review

Status: ✅ No issues found

No vulnerable or license-violating dependencies detected in this PR.
📋 View full report


Generated by Argus


Generated by Argus

X-Guardian and others added 3 commits July 1, 2026 09:19
Co-authored-by: Simon Heather <simon.heather@yulife.com>
GitLab component input names are commonly hyphenated (e.g. `job-name`,
`skip-find-images`), but parseInputsSection's input-key regex only allowed
`[a-zA-Z0-9_]`. Hyphenated keys weren't detected as new inputs, so their
`description:`/`default:` lines bled onto the previous non-hyphenated input
and every field after it shifted (e.g. `architecture` showed a later input's
description). Add `-` to the name class so each input maps to its own fields.
Comments and blank lines were already filtered and are unaffected.

Adds a regression test with hyphenated names interspersed with comment and
blank lines.

Fixes #211

Co-authored-by: eFAILution <eFAILution@users.noreply.github.com>
eFAILution and others added 5 commits July 6, 2026 15:22
…mantic-release) (#213)

The docs claimed releases run via semantic-release on merge. That's inaccurate —
semantic-release isn't a dependency. The actual flow:
- Versioning is release-it: ci.yml's `release` job runs `release-it --ci` on push
  to beta/main to bump the version, update CHANGELOG, and push a
  `chore(release): <version> [skip ci]` commit + tag.
- Publishing is a manual `workflow_dispatch` (Publish / Publish Beta), gated by
  branch, version-match, release-commit HEAD, tests, npm audit, gitleaks, and the
  even(stable)/odd(pre-release) minor convention, then `vsce publish`.

Changes:
- replace docs/SEMANTIC_RELEASE.md with docs/RELEASING.md (the old file documented
  non-existent `semantic-release:*` npm scripts)
- fix the README Contributing paragraph, AGENTS.md tech-stack + release lines, and
  the .ai/workflows.yaml release steps

Co-authored-by: eFAILution <eFAILution@users.noreply.github.com>
The pre-commit suite (wired into husky's prepare-commit-msg) failed on
tests/fixtures/** — intentionally-crafted GitLab CI parser inputs. yamllint
flagged flow-style braces ({ job_name: deploy }) and empty values (region:),
while trailing-whitespace/end-of-file-fixer rewrote the deliberate trailing
whitespace and blank lines those completion/parser tests depend on.

- .yamllint.yml: ignore tests/fixtures/** (braces reverted to default enable)
- .pre-commit-config.yaml: exclude tests/fixtures/ from trailing-whitespace,
  end-of-file-fixer, and mixed-line-ending
- tsconfig.tests.json: conform to pretty-format-json (real file that had drifted)

Fixtures are validated by the mocha suite (306 passing), not by style linters.
Note: yamllint/pre-commit run only in the local hook, not in GitHub Actions CI.

Co-authored-by: eFAILution <eFAILution@users.noreply.github.com>
eFAILution and others added 2 commits July 7, 2026 08:51
…redentials cross-origin (#222)

Previously any 3xx was treated as an error, so moved GitLab component projects failed to fetch. Add a credential-safe redirect policy: follow only same-origin redirects with headers intact, strip Authorization/PRIVATE-TOKEN/Cookie on cross-origin hops, refuse HTTPS->HTTP downgrades, and cap the chain at MAX_REDIRECTS. This prevents the user's GitLab token from being replayed to an attacker-controlled Location (e.g. after a moved project's old path is reclaimed).

The policy lives in a new pure, unit-tested src/utils/redirectPolicy.ts (httpClient was already over the file-size limit). Refs #221.

Co-authored-by: eFAILution <eFAILution@users.noreply.github.com>
@eFAILution
eFAILution deployed to publish-beta July 7, 2026 13:01 — with GitHub Actions Active
@eFAILution

Copy link
Copy Markdown
Owner Author

@X-Guardian are you seeing any issues with the latest pre-release? I had to reset the cache to gain back full functionality. The new blob settings are working great.

@X-Guardian

Copy link
Copy Markdown
Contributor

I've got a couple of minor issues that I was intending to sort out, but I don't think they are worth holding up the next release.

  • The component link URLs in a file aren't activated until the file is edited.
  • Remove the 'Component/Project does not have a description' text.

eFAILution and others added 2 commits July 8, 2026 08:20
Removing the custom gitlab-ci language (#210) dropped recognition of files like deploy.gitlab-ci.yml: the old language matched them via its extensions (a filename-suffix match), but the replacement path globs only matched a file named exactly .gitlab-ci.yml. Such files opened as yaml and fell out of scope, so hover/completion stopped firing and the isCiFile-gated Browse Components menu was hidden. Restore the suffix by adding **/*.gitlab-ci.yml and **/*.gitlab-ci.yaml to the defaults; add regression tests plus an over-match guard.

Co-authored-by: eFAILution <eFAILution@users.noreply.github.com>
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.

2 participants