Skip to content

feat(aurelia): pin aurelia package versions#170

Open
Vheissu wants to merge 1 commit into
masterfrom
feat/issue-169
Open

feat(aurelia): pin aurelia package versions#170
Vheissu wants to merge 1 commit into
masterfrom
feat/issue-169

Conversation

@Vheissu
Copy link
Copy Markdown
Member

@Vheissu Vheissu commented Jun 1, 2026

Add a central set of pinned Aurelia package versions and expose them as template properties so generated projects use exact pins instead of dist‑tags. Provide a script to verify or update those pins from npm and wire the properties into the preset picker (including unattended flows). Remove the interactive Aurelia release prompt and add tests to validate version pins and questionnaire behaviour to improve reproducibility and enforce pre‑release checks.

Closes issue #169

Add a central set of pinned Aurelia package versions and expose them as template properties so generated projects use exact pins instead of dist‑tags. Provide a script to verify or update those pins from npm and wire the properties into the preset picker (including unattended flows). Remove the interactive Aurelia release prompt and add tests to validate version pins and questionnaire behaviour to improve reproducibility and enforce pre‑release checks.
@Vheissu Vheissu requested a review from 3cp June 1, 2026 06:02
@3cp
Copy link
Copy Markdown
Member

3cp commented Jun 2, 2026

Few discussions:

  1. does this mean that we need to update that 2.0.0-rc.1 in aurelia-versions.js everytime when we release a new version?
    • it's possible to utilise before.js to check npm registry in real time to get latest aurelia packages version number, and put them into the template variables.
  2. should not we use "^2.x.x" in the final package.json, instead of "2.x.x"?

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