Skip to content

[release] Prepare for 0.15.0 release #76

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

Merged
merged 2 commits into from
Dec 27, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,23 @@
# Change Log

## 0.15.0 (2024-12-27)

No new functionality in this release but an update to the supported versions.

Thanks to [Moosieus](https://github.com/Moosieus) Patch now compiles cleanly on Elixir 1.9+ with the removal of some outdated language constructs in favor of more modern constructs.

0.15.0 removes support for Elixir 1.7 (released in July of 2018) and 1.8 (released in January of 2019). This version also adds 1.17 and 1.18 to the support matrix.

If you are still running on 1.7 or 1.8 you should continue to use the 0.14.0 release, if you require ongoing support you should open an issue to discuss.

### Improvements

- ⬆️ - \[Versions\] Elixir 1.17 and 1.18 are now supported and part of CI.

### Breaking Changes

- 💔 - Elixir 1.7 and Elixir 1.8 are no longer supported.

## 0.14.0 (2024-10-15)

Changes where mocks are evaluated to prevent misuse and allow for common patterns that were not previously supported.
Expand Down Expand Up @@ -128,6 +146,7 @@ Minor fix to `.formatter.exs`. Exported format options were not being honored b
### Improvements

- ⬆️ - \[Change Log\] Removed sections that have no content, except for `Breaking Changes`. Sections will only be included in the Change Log if some change has actually occurred. To aid developers upgrading where between versions where breaking changes are allowed, `Breaking Changes` will be included when there are no breaking changes with the description `None` to clearly indicate that no breaking changes have occurred.

### Bugfixes

- 🐞 - Fixed the `.formatter.exs` so assertion functions won't be parenthesized by projects using `import_deps`
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ Add patch to your mix.exs
```elixir
def deps do
[
{:patch, "~> 0.14.0", only: [:test]}
{:patch, "~> 0.15.0", only: [:test]}
]
end
```
Expand Down
2 changes: 1 addition & 1 deletion config/test.exs
Original file line number Diff line number Diff line change
@@ -1 +1 @@
import Mix.Config
import Config
2 changes: 1 addition & 1 deletion mix.exs
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ defmodule Patch.MixProject do
def project do
[
app: :patch,
version: "0.14.0",
version: "0.15.0",
elixir: "~> 1.9",
erlc_paths: erlc_paths(Mix.env()),
elixirc_paths: elixirc_paths(Mix.env()),
Expand Down
2 changes: 1 addition & 1 deletion pages/cheatsheet.cheatmd
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ In the `deps/0` function in the mix.exs file add a line for Patch.
```elixir
def deps do
[
{:patch, "~> 0.14.0", only: [:test]}
{:patch, "~> 0.15.0", only: [:test]}
]
end
```
Expand Down