chore(release): prepare 3.1.15

[ifBars]

Summary

• bump the S1API project and Melon metadata to 3.1.15
• add curated 3.1.15 release notes for the custom NPC inventory, relationship, and accepted-deal persistence fixes in Fix custom dealer inventory restoration after reload #261 and fix: persist custom NPC deals and relationships #262
• teach the GitHub release workflow to publish versioned curated notes when present while retaining generated notes as a fallback for historical/manual reruns
• document the curated-notes step in the branch-based release policy

Validation

• MonoMelon solution build: 0 warnings, 0 errors
• MonoMelon tests: 575/575 passed
• Il2CppMelon solution build: 0 warnings, 0 errors
• Il2CppMelon tests: 564/564 passed
• workflow YAML parsed successfully
• curated and fallback release-note paths executed successfully with Bun
• project, Melon, and generated package versions resolve to 3.1.15

Release flow

After this PR merges with a merge commit, releases/3.1.15 will be fast-forwarded to the resulting stable commit and that exact shared commit will be tagged v3.1.15.

Summary by CodeRabbit

• Release
  • Released version 3.1.15.
  • Added curated release notes covering persistence for custom NPC inventories, relationships, deals, and unlocks.
  • Included compatibility and validation details, contributor credits, and release links.
• Documentation
  • Clarified release procedures and standardized the format and availability of release notes.
  • Improved release announcements by using curated notes when available, with generated notes as a fallback.

[coderabbitai]

Warning

Review limit reached

@ifBars, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4d0e9cc1-5b8c-4087-b1f6-16b068c48581

📥 Commits

Reviewing files that changed from the base of the PR and between 165ed5e and 2123922.

📒 Files selected for processing (1)

• VERSIONING.md

📝 Walkthrough

Walkthrough

This release updates S1API to version 3.1.15, adds curated release notes, changes GitHub release publishing to use version-specific notes, and documents the updated release and hotfix procedures.

Changes

Release version and publishing

Layer / File(s)	Summary
Release inputs and version metadata .github/release-notes/3.1.15.md, S1API/S1API.cs, S1API/S1API.csproj	Adds curated 3.1.15 release notes and updates assembly and package versions.
Curated note selection .github/workflows/publish-github-release.yml	Passes the release version to the publishing script, validates curated notes, falls back when notes are missing, and uses the selected notes in the release payload.
Release procedure documentation VERSIONING.md	Documents curated note requirements for releases and hotfixes, including required sections and fallback behavior.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Workflow as publish-github-release.yml
  participant Notes as Curated release notes
  participant GitHub as GitHub release API
  Workflow->>Notes: Read notes for RELEASE_VERSION
  Notes-->>Workflow: Return content or missing-file result
  Workflow->>GitHub: Publish selected release_notes

Loading

Possibly related PRs

• ifBars/S1API#184: Both modify GitHub release workflow note handling.
• ifBars/S1API#256: Both update S1API version metadata.
• ifBars/S1API#175: Both update version metadata for a release.

Suggested reviewers: doodesch

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the release-preparation change and specifies version 3.1.15.
Description check	✅ Passed	The description clearly covers the release scope, validation results, and release flow, but it omits explicit Compatibility and Documentation sections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@VERSIONING.md`:
- Around line 120-121: Update the stale release-note behavior statement in
VERSIONING.md to say that the workflow publishes the versioned curated Markdown
as the GitHub release body when the file exists, and falls back to
GitHub-generated notes only when it is absent.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ab355bb2-e569-4d17-a4e8-4f2fa79849d1

📥 Commits

Reviewing files that changed from the base of the PR and between dab5bd3 and 165ed5e.

📒 Files selected for processing (5)

• .github/release-notes/3.1.15.md
• .github/workflows/publish-github-release.yml
• S1API/S1API.cs
• S1API/S1API.csproj
• VERSIONING.md