Appsignal

_Published on 2024-01-19._

Added

- [e712276](https://github.com/appsignal/mono//commit/e71227686606d317e5f79663e51e0c49e6a47240) minor - Support custom languages with the custom language option. Example custom language configuration:

yaml
---
language: custom
repo: "https://github.com/appsignal/appsignal-python"
bootstrap:
command: "echo bootstrap"
clean:
command: "hatch clean"
build:
command: "hatch build"
publish:
command: "hatch publish"
test:
command: "hatch run test:pytest"
read_version: "hatch version"
write_version: "hatch version"

- [7853508](https://github.com/appsignal/mono//commit/7853508c106f16e8c9d7a11741e420b5f70c3701) minor - Add mono publish `--no-git` flag. When this flag is given to `mono publish`, the publishing process will not commit the changes to Git, create a tag or push the changes to the remote. This can be useful when you want mono to only generate changelogs and update package version.
- [10ce9e4](https://github.com/appsignal/mono//commit/10ce9e44e3f271ac240aaeefb274b45a05114c6b) minor - Add mono publish `--no-package-push` flag. When this flag is given to `mono publish`, the publishing process will not push the packages to their version managers. This can be useful when you want mono to only generate changelogs and update package version.
- [cbd946d](https://github.com/appsignal/mono//commit/cbd946d3f844b514dc5dcd43b53d83dddc9a9dc7) minor - Add mono publish `--yes` flag. When this flag is given to `mono publish`, the publishing process will not prompt to confirm publishing. Any OTP prompts by the package managers may still prompt for input.
- [d7ab1e0](https://github.com/appsignal/mono//commit/d7ab1e08b5140718bb09075691e6d9969d95a938) patch - Support custom tags for Node.js packages. Call `mono publish` with the `--tag` option to set custom tags for new releases. By default Node.js adds the `latest` tag to new releases, but this may not always be desired. The tag specified applies to all packages published by mono. The `--tag` option has precedence over the `--prerelease` option.


mono publish --tag 2.x-stable

- [7837ef1](https://github.com/appsignal/mono//commit/7837ef18308d4bd9b77e677b49288f66a70ff12b) patch - When the `mono publish` command fails at or before the publishing step, offer the user the possibility to rollback changes performed to the Git repository.

Changed

- [56d7135](https://github.com/appsignal/mono//commit/56d71351d37cc7ee615061e368b08f16cd3ca68a) minor - Require Ruby 3 going forward.
- [8ae7c7f](https://github.com/appsignal/mono//commit/8ae7c7f19b807ea19e9631646efb6bf6d27e0a37) minor - Use a selection prompt for the semver change in `mono changeset add`. The prompts were inconsistency asking between a number and text input. It now will only require you to select options with numbers.
- [19eb6f7](https://github.com/appsignal/mono//commit/19eb6f7b8881d90ff940ab6be064a33840b3b80f) patch - Remove [ci skip] tag from publish commit. Run the CI build for the publish commit just in case anything could break with updating the version.
- [4e21aed](https://github.com/appsignal/mono//commit/4e21aed834c3fb5655832ecbc37da89743e08e7b) patch - Improve publish commit message. When only one package is publish, show the version number in the commit subject. Add a small description to the message what was changed.
- [b0474af](https://github.com/appsignal/mono//commit/b0474af63cfea06bda0598b7b7db7ed4bdb9375c) patch - When running `mono publish`, check if the Git tag that is about to be published already exists, and if so, abort the publishing process early.
- [ad5a451](https://github.com/appsignal/mono//commit/ad5a4515a4f4bd114b180db33d20ed0422a8c9e9) patch - Add the publish date for each version to the changelog. This allows people to see at a glance when a version was released.

Fixed

- [db13740](https://github.com/appsignal/mono//commit/db137400a7db78481866bbccc751c6abde4f99fa) patch - Fix changeset filenames containing a backticks by replacing it with a dash (`-`). If a backtick was present in the changeset description it would fail to open the right file when prompted.
- [6596f02](https://github.com/appsignal/mono//commit/6596f02435862edcd32444442545109b45f8b185) patch - Check if the directory in which Mono is run is Mono project before performing commands. Previously Mono would error with a non-user friendly Ruby error about a missing file. This case is now handled with a better error message.

Added

- [bdbbcf5](https://github.com/appsignal/mono//commit/bdbbcf5463e496ebb2537842af8a14ac1ada16cd) patch - Support Node.js package.json `devDependencies`. Any package in the workspace that's specified as a dev dependency by other packages are also updated upon publish.

Fixed

- [546b81a](https://github.com/appsignal/mono//commit/546b81af8b5facf8a044d73b712e43566c9e66e6) patch - Strip out colons from changeset filenames. The colon and semicolon symbols are now replaced with a dash symbol.

Fixed

- [393d60d](https://github.com/appsignal/mono//commit/393d60de44fce6ad54c3c652f8e58fa9c333cdf3) patch - Fix publishing with changeset filenames containing unescaped symbols.
- [3eb2f57](https://github.com/appsignal/mono//commit/3eb2f5726a82732cc21f3cdce83b3fc621c02a31) patch - Prevent duplicate dependency bump changesets. Previously, if a package's dependency had a dependency that was also updated, the final package in the tree would track multiple changesets for the same dependency update.

Added

- [d81182b](https://github.com/appsignal/mono//commit/d81182b0921e09d0b02a514b11000c1cce5b24e3) minor - Add types to changesets. The following types are supported: add, change, deprecate, remove, fix and security. Use the appropriate one for the change and the changelog will include sections for every present type of change. This will make it easier for readers to understand the impact of a new release's changes.
- [dd19f67](https://github.com/appsignal/mono//commit/dd19f67c7cedc2d472e3950fe59860473d625d8a) minor - Add support for the `fish` shell in the `script/setup` installation script.
- [dd19f67](https://github.com/appsignal/mono//commit/dd19f67c7cedc2d472e3950fe59860473d625d8a) patch - Print changeset summaries on publish. This makes it easier to tell which changes are about to be published for every package.
- [dd19f67](https://github.com/appsignal/mono//commit/dd19f67c7cedc2d472e3950fe59860473d625d8a) patch - Print changeset type on publish preview.

Fixed

- [81b0614](https://github.com/appsignal/mono//commit/81b06140acd7ab8823627b28a8cb6d18546d7cd1) patch - Validate changesets when parsing. With the addition of changeset types, make sure that the changesets have a version bump and type specified and that they are known values. Otherwise, these changesets would not be picked up by mono.
- [dd19f67](https://github.com/appsignal/mono//commit/dd19f67c7cedc2d472e3950fe59860473d625d8a) patch - Validate user input of the package number for changesets in mono repositories better. Non number characters and other invalid strings will prompt the user again to enter a valid package number.

- [616571e](https://github.com/appsignal/mono//commit/616571e8aebb77ab2aa9240ae803e0636aeb9bf1) patch - Add `mono-dev` executable to allow for testing mono. The `mono` executable will not allow usage of mono with uncommitted changes. This will prevent accidental usage of mono with uncommitted changes that would cause mono to crash unexpectedly.
- [43cc5fc](https://github.com/appsignal/mono//commit/43cc5fc133afd6faccecc1e6c966a5c0bb0bd279) patch - Retry failed publish commands. When a publish command like `gem push` fails, prompt the user to retry it rather than fail the entire publish process.
- [709caa4](https://github.com/appsignal/mono//commit/709caa41acba2a1e2f352db885570680b48f46ae) patch - Fix mono production check directory. It would perform the check in the current directory, not the mono install directory.
- [f70a877](https://github.com/appsignal/mono//commit/f70a877adb7f36e30a63acf104bb119da4e8d588) patch - Check Git branch for mono to prevent accidental usage of mono on an unmerged branch.
- [e89e57c](https://github.com/appsignal/mono//commit/e89e57c88f7df7281531da6fdb37010e67fa7461) patch - Skip Git check if Git command fails. If `git status` fails in the `mono` directory, skip the check. It's probably a production download.

- [244ec4f](https://github.com/appsignal/mono//commit/244ec4f633754c9f1f85578fbc1fb00ce0843401) patch - Aside from working on Elixir projects with their version set in a module attribute (`version "1.2.3"` and `version: version`), add support for projects with their versions set directly in the `project` block (`version: "1.2.3"`).
- [221dd5f](https://github.com/appsignal/mono//commit/221dd5f705b4aaec462b6fa500f3669b2def3c60) patch - Move the [ci-ckip] tag to commit message body instead of printing it in the subject.
- [940b0ac](https://github.com/appsignal/mono//commit/940b0acac4580bada23ba2989f1413ce0e425db5) patch - Fix Node.js package publishing using yarn. Calling `yarn publish` prompted the user to enter a new version while Mono already knows what version to upgrade the package to. This prompt is now removed.