discourse/app/assets/javascripts/admin/config/ember-cli-update.json

{
  "schemaVersion": "1.0.0",
  "packages": [
    {
      "name": "ember-cli",
      "version": "5.0.0",
      "blueprints": [
        {
          "name": "addon",
          "outputRepo": "https://github.com/ember-cli/ember-addon-output",
          "codemodsSource": "ember-addon-codemods-manifest@1",
          "isBaseBlueprint": true,
          "options": [
            "--no-welcome"
          ]
        }
      ]
    }
  ]
}
DEV: Upgrade to Ember 3.28 2022-07-18 10:14:37 +01:00			`{`
			`"schemaVersion": "1.0.0",`
			`"packages": [`
			`{`
			`"name": "ember-cli",`
DEV: Update ember-cli to 5.0.0 (#22280) 2023-06-26 17:15:59 +02:00			`"version": "5.0.0",`
DEV: Upgrade to Ember 3.28 2022-07-18 10:14:37 +01:00			`"blueprints": [`
			`{`
			`"name": "addon",`
			`"outputRepo": "https://github.com/ember-cli/ember-addon-output",`
			`"codemodsSource": "ember-addon-codemods-manifest@1",`
			`"isBaseBlueprint": true,`
DEV: Update ember-cli to 4.12.0 (#21074) It's backward compatible so still supports our 3.28 ember-source. The visible change is finally getting rid of this message: ``` WARNING: Node v18.12.0 is not tested against Ember CLI on your platform. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details. ``` --- `@ember/string` dependency is added for future compatibility. See: https://github.com/ember-cli/ember-cli/pull/10125 --- `tests/helpers/index.js` is unused for now, but is a nice pattern. We could move some of our test setup into local `setupApplicationTest/setupRenderingTest/setupTest` helpers. Co-authored-by: David Taylor <david@taylorhq.com> 2023-04-19 12:58:29 +02:00			`"options": [`
			`"--no-welcome"`
			`]`
DEV: Upgrade to Ember 3.28 2022-07-18 10:14:37 +01:00			`}`
			`]`
			`}`
			`]`
			`}`