DEV: Introduce feature-flag for Ember 5 upgrade
This commit introduces the scaffolding for us to easily switch between Ember 3.28 and Ember 5 on the `main` branch of Discourse. Unfortunately, there is no built-in system to apply this kind of flagging within yarn / ember-cli. There are projects like `ember-try` which are designed for running against multiple version of a dependency, but they do not allow us to 'lock' dependency/sub-dependency versions, and are therefore unsuitable for our use in production.
Instead, we will be maintaining two root `package.json` files, and two `yarn.lock` files. For ember-3, they remain as-is. For ember5, we use a yarn 'resolution' to override the version for ember-source across the entire yarn workspace.
To allow for easy switching with minimal diff against the repository, `package.json` and `yarn.lock` are symlinks which point to `package-ember3.json` and `yarn-ember3.lock` by default. To switch to Ember 5, we can run `script/switch ember version 5` to update the symlinks to point to `package-ember5.json` and `package-ember3.json` respectively. In production, and when using `bin/ember-cli` for development, the ember version can also be upgraded using the `EMBER_VERSION=5` environment variable.
When making changes to dependencies, these should be made against the default `ember3` versions, and then `script/regen_ember_5_lockfile` should be used to regenerate `yarn-ember5.lock` accordingly. A new 'Ember Version Lockfiles' GitHub workflow will automate this process on Dependabot PRs.
When running a local environment against Ember 5, the two symlink changes will show up as git diffs. To avoid us accidentally committing/pushing that change, another GitHub workflow is introduced which checks the default Ember version and raises an error if it is greater than v3.
Supporting two ember versions simultaneously obviously carries significant overhead, so our aim will be to get themes/plugins updated as quickly as possible, and then drop this flag.
2023-11-27 10:52:17 -05:00
|
|
|
# This workflow is designed to stop us accidently committing the lockfile/packagejson symlink changes
|
|
|
|
|
# which would cause the default Ember version to change.
|
|
|
|
|
|
|
|
|
|
name: Ember Version Enforcement
|
|
|
|
|
|
|
|
|
|
on:
|
|
|
|
|
pull_request:
|
|
|
|
|
push:
|
|
|
|
|
branches:
|
|
|
|
|
- main
|
|
|
|
|
|
|
|
|
|
permissions:
|
|
|
|
|
contents: write
|
|
|
|
|
|
|
|
|
|
jobs:
|
|
|
|
|
check:
|
|
|
|
|
runs-on: ubuntu-latest
|
|
|
|
|
steps:
|
|
|
|
|
- uses: actions/checkout@v4
|
|
|
|
|
- name: Setup Node
|
2023-11-28 04:57:28 -05:00
|
|
|
uses: actions/setup-node@v4
|
DEV: Introduce feature-flag for Ember 5 upgrade
This commit introduces the scaffolding for us to easily switch between Ember 3.28 and Ember 5 on the `main` branch of Discourse. Unfortunately, there is no built-in system to apply this kind of flagging within yarn / ember-cli. There are projects like `ember-try` which are designed for running against multiple version of a dependency, but they do not allow us to 'lock' dependency/sub-dependency versions, and are therefore unsuitable for our use in production.
Instead, we will be maintaining two root `package.json` files, and two `yarn.lock` files. For ember-3, they remain as-is. For ember5, we use a yarn 'resolution' to override the version for ember-source across the entire yarn workspace.
To allow for easy switching with minimal diff against the repository, `package.json` and `yarn.lock` are symlinks which point to `package-ember3.json` and `yarn-ember3.lock` by default. To switch to Ember 5, we can run `script/switch ember version 5` to update the symlinks to point to `package-ember5.json` and `package-ember3.json` respectively. In production, and when using `bin/ember-cli` for development, the ember version can also be upgraded using the `EMBER_VERSION=5` environment variable.
When making changes to dependencies, these should be made against the default `ember3` versions, and then `script/regen_ember_5_lockfile` should be used to regenerate `yarn-ember5.lock` accordingly. A new 'Ember Version Lockfiles' GitHub workflow will automate this process on Dependabot PRs.
When running a local environment against Ember 5, the two symlink changes will show up as git diffs. To avoid us accidentally committing/pushing that change, another GitHub workflow is introduced which checks the default Ember version and raises an error if it is greater than v3.
Supporting two ember versions simultaneously obviously carries significant overhead, so our aim will be to get themes/plugins updated as quickly as possible, and then drop this flag.
2023-11-27 10:52:17 -05:00
|
|
|
with:
|
|
|
|
|
node-version: 20
|
|
|
|
|
cache: yarn
|
|
|
|
|
- name: Yarn install
|
|
|
|
|
run: |
|
|
|
|
|
cd app/assets/javascripts/discourse
|
|
|
|
|
yarn install
|
|
|
|
|
- name: "Check default ember version"
|
|
|
|
|
working-directory: app/assets/javascripts/discourse
|
|
|
|
|
run: |
|
|
|
|
|
node -e '
|
|
|
|
|
const version = require("ember-source/package.json").version;
|
|
|
|
|
console.log("Ember version is", version);
|
|
|
|
|
if(version.split(".")[0] !== "3"){
|
|
|
|
|
console.log(`Ember has unexpectedly been upgraded to version ${version}. If this is intentional, remove this github workflow.`);
|
|
|
|
|
process.exit(1);
|
|
|
|
|
}
|
|
|
|
|
'
|
|
|
|
|
- name: Upgrade ember
|
|
|
|
|
run: |
|
|
|
|
|
script/switch_ember_version 5
|
|
|
|
|
cd app/assets/javascripts/discourse
|
|
|
|
|
yarn install
|
|
|
|
|
- name: "Check upgraded version"
|
|
|
|
|
working-directory: app/assets/javascripts/discourse
|
|
|
|
|
run: |
|
|
|
|
|
node -e '
|
|
|
|
|
const version = require("ember-source/package.json").version;
|
|
|
|
|
console.log("Ember version is", version);
|
|
|
|
|
if(version.split(".")[0] !== "5"){
|
|
|
|
|
console.log(`Expected Ember 5, but found ${version}`);
|
|
|
|
|
process.exit(1);
|
|
|
|
|
}
|
|
|
|
|
'
|
