Bump @actions/languageserver and @actions/workflow-parser to 0.3.30 #544
Conversation
There was a problem hiding this comment.
Pull request overview
This PR bumps the @actions/languageserver and @actions/workflow-parser dependencies from version 0.3.19 to 0.3.30, bringing in numerous improvements and bug fixes for GitHub Actions workflow support in VS Code.
- Updates two core dependencies to version 0.3.30
- Adds comprehensive changelog entry documenting 29 new features and fixes from the upstream libraries
- Updates transitive dependencies and lock file accordingly
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Bumps @actions/languageserver and @actions/workflow-parser from ^0.3.19 to ^0.3.30 |
| package-lock.json | Updates lock file with new versions, integrity hashes, and transitive dependency changes including @actions/expressions and @actions/languageservice; adds peer dependency markers and license fields |
| CHANGELOG.md | Adds version 0.28.3 entry documenting all features and fixes from the dependency updates, including improved completions, validation, diagnostics, and support for new GitHub Actions features |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - Cron schedule descriptions now appear as inlay hints instead of info diagnostics | ||
| - Add runs-on label completions for mapping syntax | ||
| - Fix autocomplete showing mapping keys for empty values | ||
| - Use detail field for one-of qualifiers instead of label | ||
| - Add escape hatch completions to switch structural forms | ||
| - Remove invalid autocomplete options for committed structural types | ||
| - Add warning for short SHA refs in `uses` | ||
| - Expand one-of keys to multiple completion items | ||
| - Support for `job.check_run_id` context | ||
| - Add language server executable | ||
| - Add `ubuntu-slim` and updated runner labels | ||
| - ESM migration: Add .js extensions for node16 moduleResolution | ||
| - Fix one-of property completions to insert value on next line | ||
| - Add missing activity types for `pull_request` and `pull_request_target` | ||
| - Support YAML anchors and aliases | ||
| - Always provide strategy and matrix contexts with defaults | ||
| - Suppress warnings for step output property access | ||
| - Add concurrency deadlock detection validation | ||
| - Fix expression completion in multi-line if block scalars | ||
| - Add missing runner context properties (environment, debug, workspace) | ||
| - Allow empty strings in `workflow_dispatch` choice options | ||
| - Skip validation for dynamic environments | ||
| - Skip secrets/vars validation when context is incomplete | ||
| - Optimize JSON data files to reduce bundle size by 90% | ||
| - Improve cron schedule warning message | ||
| - Add validation for literal text in if conditions | ||
| - Add `uses` syntax validation for step and job-level workflows | ||
| - Fix misleading error for malformed local workflow paths | ||
| - Improve cron schedule validation and diagnostics |
There was a problem hiding this comment.
The backticks are inconsistent around code-like terms in the changelog entries. Some entries use backticks for terms like 'uses', 'job.check_run_id', 'ubuntu-slim', 'pull_request', 'workflow_dispatch' while others use plain text for similar terms like 'runs-on', 'one-of', or 'step output'. Consider consistently using backticks for all code-like terms (keywords, property names, event names, context names, etc.) throughout the changelog for better readability and consistency with the established pattern in other entries.
No description provided.