[PR #678] feat: add wording for deprecation warnings #654

New Issue

GiteaMirror · 2026-02-17T12:11:08-06:00

GiteaMirror commented

2026-02-17 12:11:08 -06:00

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/678
Author: @anagno
Created: 12/23/2025
Status: 🔄 Open

Base: master ← Head: feat/deprecate

📝 Commits (1)

9860eb5 feat: add wording for deprecation warnings

📊 Changes

1 file changed (+31 additions, -5 deletions)

View changed files

📝 content/next/index.md (+31 -5)

📄 Description

Hello Everyone,

This PR adds the handling of deprecations warnings.

Semantic version already has a clear way on how to handle deprecation warning, but there isn`t a standarized way on declaring them in our commit messages.

Treat this PR as suggestion, that wants to start the discussion on how to handle deprecations warnings and see if we can reach an aggrement on how to handle them.

Closes #557

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/conventional-commits/conventionalcommits.org/pull/678 **Author:** [@anagno](https://github.com/anagno) **Created:** 12/23/2025 **Status:** 🔄 Open **Base:** `master` ← **Head:** `feat/deprecate` --- ### 📝 Commits (1) - [`9860eb5`](https://github.com/conventional-commits/conventionalcommits.org/commit/9860eb582fc9050669d4b6cc06948228fd3dc2b7) feat: add wording for deprecation warnings ### 📊 Changes **1 file changed** (+31 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `content/next/index.md` (+31 -5) </details> ### 📄 Description Hello Everyone, This PR adds the handling of deprecations warnings. Semantic version already has a clear way on how to handle [deprecation warning](https://semver.org/#how-should-i-handle-deprecating-functionality), but there isn`t a standarized way on declaring them in our commit messages. Treat this PR as suggestion, that wants to start the discussion on how to handle deprecations warnings and see if we can reach an aggrement on how to handle them. Closes #557 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-02-17 12:11:08 -06:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#654