Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate add-on to v2 format & upgrade to Ember.js v5.4.1 #299

Merged
merged 10 commits into from
Dec 2, 2023

Conversation

MrChocolatine
Copy link
Member

@MrChocolatine MrChocolatine commented Nov 5, 2023

Breaking

Migrate add-on to v2 format (#299)

The add-on is now a full v2 add-on, it was recreated as such using Embroider and the latest specifications.

ember addon myaddon --blueprint @embroider/addon-blueprint --typescript --yarn

Upgrade to Ember.js v5.4.1 (#299)

  • Ember.js v4.8 or above is now required
  • Embroider or ember-auto-import v2 are now required

Closes #279 .


Below is just extra text to give more context, but it should not be included in our changelog.

Actions taken

  1. Fresh add-on created using the latest version of Ember.js + flag --typescript + v2 blueprint from Embroider
  2. Then re-import everything from our add-on
  3. Re-adjust a few things to make it work for our setup

Resources

@MrChocolatine MrChocolatine added dependencies Changes that update dependencies ci Changes related to the CI documentation Changes in documentation breaking Breaking changes labels Nov 5, 2023
@MrChocolatine MrChocolatine requested a review from a team as a code owner November 5, 2023 21:26
@MrChocolatine MrChocolatine force-pushed the upgrade-latest-emberjs-version branch from da30ca6 to 99e97f2 Compare November 5, 2023 21:28
@MrChocolatine MrChocolatine changed the title Migrate add-on to v2 format & upgrade to Ember.js v5.4.0 WIP // Migrate add-on to v2 format & upgrade to Ember.js v5.4.0 Nov 5, 2023
@MrChocolatine MrChocolatine force-pushed the upgrade-latest-emberjs-version branch 5 times, most recently from c19688b to b49a4ca Compare November 5, 2023 22:19
@MrChocolatine MrChocolatine force-pushed the upgrade-latest-emberjs-version branch from b49a4ca to c502a06 Compare November 5, 2023 22:32
Copy link
Member Author

@MrChocolatine MrChocolatine Nov 6, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This folder is the test application, which is internal and not what the end users will use, so in the package.json file we don't need any of the usual information like author, description etc...

@MrChocolatine MrChocolatine changed the title WIP // Migrate add-on to v2 format & upgrade to Ember.js v5.4.0 Migrate add-on to v2 format & upgrade to Ember.js v5.4.0 Nov 11, 2023
@MrChocolatine MrChocolatine force-pushed the upgrade-latest-emberjs-version branch 2 times, most recently from 9b159a8 to cc8e480 Compare November 11, 2023 17:54
@MrChocolatine MrChocolatine force-pushed the upgrade-latest-emberjs-version branch from cc8e480 to c64028d Compare November 19, 2023 12:42
@MrChocolatine MrChocolatine force-pushed the upgrade-latest-emberjs-version branch from c64028d to 919798b Compare November 27, 2023 10:41
@MrChocolatine
Copy link
Member Author

We have to move forward @DazzlingFugu/emberenos , please review.
It has been 3 weeks.

Copy link

@Pixelik Pixelik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couldn't manage to install locally and test but as long as automated tests are passing I'm fine with unblocking this 👍

@MrChocolatine MrChocolatine changed the title Migrate add-on to v2 format & upgrade to Ember.js v5.4.0 Migrate add-on to v2 format & upgrade to Ember.js v5.4.1 Nov 30, 2023
See: https://github.com/embroider-build/addon-blueprint

BREAKING CHANGE: migrate add-on to v2 format & upgrade to Ember.js v5.4.0

- Now require Ember.js v4.8 or above
- Now require Embroider or ember-auto-import v2
There were some warnings when running `npm publish --dry-run`:

```
➜  npm publish --dry-run
npm WARN publish npm auto-corrected some errors in your package.json when publishing.  Please run "npm pkg fix" to address these errors.
npm WARN publish errors corrected:
npm WARN publish "repository" was changed from a string to an object
npm WARN publish "repository.url" was normalized to "git+https://github.com/DazzlingFugu/ember-slugify.git"
npm notice

... logs ...
```
This resolution was introduced in:
#116
These are not necessary.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Breaking changes ci Changes related to the CI dependencies Changes that update dependencies documentation Changes in documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

README.md is not visible on NPM
2 participants