chore: make release-able by fixing repository in package.json

[chriskrycho]

Without this:

ERROR npm warn publish npm auto-corrected some errors in your package.json when publishing.  Please run "npm pkg fix" to address these errors.

Doing so results in this change.

[chriskrycho]

@jrjohnson before we release this, I think it needs some basic maintenance—probably mostly just a bunch of dep updates. I am happy to take a little time to review that kind of maintenance PR, so feel free to ping me—but we should definitely do that before trying to release this, because we will otherwise likely just be foisting these exact issues on downstream consumers. Going to mark this particular PR as blocked until that’s the case, and we also will not be able to do a release until then!

[chriskrycho]

@jrjohnson this landed; anything else you think should be done before releasing a v3.0.0? (I’m not in a hurry, it can be tomorrow or later this week!)

[jrjohnson]

I think this is ready for v3 release.
I'll follow up with a switch to pnpm and then see where that leave #66 and the move to a v2 addon (which may be unlocked with the blueprint updates, or pnpm). I think both of those are a good candidate for a second breaking major 4.0.0 just to spread things out if that's ok with you.

[chriskrycho]

@jrjohnson I infer your thinking here is that way people on Ember v6 could upgrade to ember-render-modifiers v3 even if they’re not ready to consume a v2 addon, and then once they are, go ahead and upgrade to ember-render-modifiers v4? Assuming so, that seems reasonable to me. Once you confirm, I’ll do a release. 👍🏼

[jrjohnson]

Oooh that too 😁, I was just worried about too much change all in one release. But we absolutely should have a release for non-v2-addon, but yes Ember 6, apps.