No CHANGELOG

[scottkidder]

Hello,
Shouldn't there be somewhere to see a list of changes between releases? I understand this is supposed to be in GitHub releases, but there is nothing there for 0.4.10. The number of changes between 0.4.9 and 0.4.10 is significant and I immediately ran into issues with no where to look to see what may have caused them.

[samselikoff]

Sorry about that Scott! I stopped keeping the changes in CHANGELOG because I didn't like creating new commits after a version was cut just to update the log.

My apologies for not putting any notes in the 4.10 release, but it should have just been bugfixes. I will start putting a link to the list of commits between releases in the release notes, so you can easily browse the commits.

As far as your bug(s), what are you running into?

[nathancharles]

I am also seeing issues after upgrading from 0.4.9 to 0.4.10.

Mirage: You called server.createList('accountUsers') but no model or factory was found. Make sure you're using the singularized version of your model.

Where my model and factory are both named account-users.

It looks like pluralization of records changed when creating or referencing.
9b7c295

I agree a changelog would be great. Also, a minor version bump would be best since this is a significant and breaking change.
Migrating all references like this will definitely be non-trivial for my application.

[samselikoff]

@nathancharles thanks for the report. I will change this to a deprecation and release a 4.11

[makepanic]

If you want to automate the CHANGELOG part, you could follow https://www.conventionalcommits.org/en/v1.0.0-beta.2/ as commit convention and use something like https://github.com/conventional-changelog/standard-version to bump npm version, tag version and generate updated CHANGELOG in one step.

It works pretty well for us in various projects.

[scottkidder]

I've grown to love conventional commits as well, it seems to help out even on personal projects.

[kratiahuja]

@samselikoff do you need help with changing the error to deprecation? I can pick this up as this keeps breaking for us and we have to remember to pin it to 0.4.9.

[samselikoff]

@kratiahuja Think I'll be able to get to it tonight

[samselikoff]

Just opened PR #1452

[kratiahuja]

Thanks @samselikoff

[samselikoff]

@kratiahuja @nathancharles I've just released 0.4.11, could you give it a shot and let me know if it fixes it?

[samselikoff]

Make that 0.4.12 :)

[kratiahuja]

Thanks a lot @samselikoff

[scottkidder]

The details on the latest releases look great! Thanks for being responsive on this @samselikoff

[nathancharles]

Thanks @samselikoff !