Skip to content
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
27 changes: 24 additions & 3 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,21 +46,42 @@ This project uses famous football stadiums (A-Z) that hosted FIFA World Cup matc

### Changed

- Upgrade AutoMapper from 14.x to 16.1.1 to resolve high-severity security vulnerability GHSA-rvv3-g6hj-g44x (#414)
- Rename test methods to follow Microsoft .NET naming standard (#396)

### Deprecated

### Removed

### Fixed

### Security

---

## [2.0.0 - centenario] - 2026-03-18

### Changed

- Refactor error responses to use RFC 7807 Problem Details (#418)
- Add `/squadNumber/` path segment to PUT and DELETE routes — **breaking change** (#418)
- Extract `NotFoundTitle` constant and remove redundant null-conditional operator (#418)
- Rename test methods to follow Microsoft .NET naming standard (#396)
- Upgrade AutoMapper from 14.x to 16.1.1 (#414) — see Security section
- Bump FluentAssertions from 8.8.0 to 8.9.0 (#417)
- Bump coverlet.collector from 8.0.0 to 8.0.1 (#419)
- Bump softprops/action-gh-release from 2.6.0 to 2.6.1 (#416)

### Fixed

- Add squad number mismatch guard in `PutAsync` and update README (#418)
- Strengthen test assertions for Problem Details responses (#418)
- Fix broken 201 assertion in controller test for `Post_Players_NonExisting` (#396)
- Add missing edge case tests for `UpdateAsync`, `DeleteAsync`, and
`DateOfBirth` boundary validation (#396)

### Security

- Sanitize player data before logging to prevent log forging
- Upgrade AutoMapper from 14.x to 16.1.1 to resolve high-severity security vulnerability GHSA-rvv3-g6hj-g44x (#414)

---

## [1.1.0 - bernabeu] - 2026-02-09
Expand Down
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -330,14 +330,16 @@ To create a new release, follow this workflow:

#### 1. Update CHANGELOG.md

First, document your changes in [CHANGELOG.md](CHANGELOG.md):
First, create a `release/` branch and document your changes in [CHANGELOG.md](CHANGELOG.md):

```bash
git checkout -b release/1.0.0-azteca
# Move items from [Unreleased] to new release section
# Example: [1.0.0 - azteca] - 2026-01-22
git add CHANGELOG.md
git commit -m "docs: prepare changelog for v1.0.0-azteca release"
git push
git push origin release/1.0.0-azteca
# Open a PR, get it reviewed, and merge into master
```

#### 2. Create and Push Tag
Expand Down
Loading