Joe Bottigliero

Hey! Thanks for the report. This has been asked for a few times (in slightly different ways), it's a feature (support for any file/project type) that I'd love to get...

@FixRM – if I'm not mistaking, I think what you are looking for would be a combination of the existing `--release-as` flag along with the configuration of the upcoming feature...

Hey @andykao1213 – from the standard-version (conventional-changelog) perspective if the commit is in the history (and matches the commit preset you are using) it will still be written to the...

Let me know if this looks closer to the direction you all were hoping to go with this functionality, if so, I'll get the tests cleaned up!

Thanks for the heads up @bmish; I've opened #2423, which seems closer to that desired functionality... for my use case I'll likely revert to an `allowlist`, but it seems like...

I doubt it helps narrow the cause, but figured adding the environment configuration I'm seeing this same behavior in might be better than just a "+1": [email protected] [email protected] @ember/[email protected] [email protected]...

While the referenced PR has been merged for some time (looks like it would have landed in `3.0.0`), I'm encountering a similar error in newer versions. I've tested in both...

I encountered this issue recently transitioning to GitHub pages and wanted to flag a few updates that might be relevant. GitHub has made (and is making) some improvements to Github...

Mostly that the types are changing from an explicit types to `T | undefined` which might result in Typescript errors at build time depending on usage, i.e. ```ts const token...

At a glance, it looks like you are running into a few different issues. For your `.versionrc` file, you should be using `updater` key instead of `type`: ```js { "bumpFiles":...