Compare commits
10 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
| 606fc8d4e6 | |||
| 4ee0f5c7b1 | |||
| cb061287cd | |||
| 601227c97b | |||
| ba1977422e | |||
| 16db7e0a7f | |||
| ce62257c51 | |||
| 316579c812 | |||
| 0922d51dce | |||
| 6c12d22cce |
@@ -0,0 +1,29 @@
|
|||||||
|
# CHANGELOG
|
||||||
|
|
||||||
|
<!-- version list -->
|
||||||
|
|
||||||
|
## v1.1.3 (2025-06-07)
|
||||||
|
|
||||||
|
### Bug Fixes
|
||||||
|
|
||||||
|
- **readme**: Non critical issue, but still an issue
|
||||||
|
([`cb06128`](https://github.com/muszyn/release-testing/commit/cb061287cd96aa8d841f0066a6c4f2992a82a160))
|
||||||
|
|
||||||
|
## v1.1.2 (2025-06-07)
|
||||||
|
|
||||||
|
## v1.1.1 (2025-06-07)
|
||||||
|
|
||||||
|
## v1.1.0 (2025-06-07)
|
||||||
|
|
||||||
|
### Features
|
||||||
|
|
||||||
|
- **apis**: Really big update
|
||||||
|
([`ce62257`](https://github.com/muszyn/release-testing/commit/ce62257c51dace3835683c0ba5fa62cf119be0b9))
|
||||||
|
|
||||||
|
## v1.0.0 (2025-06-07)
|
||||||
|
|
||||||
|
- Initial Release
|
||||||
|
|
||||||
|
## v1.0.0 (2025-06-07)
|
||||||
|
|
||||||
|
- Initial Release
|
||||||
@@ -0,0 +1,30 @@
|
|||||||
|
# Python Semantic Release
|
||||||
|
|
||||||
|
Basically the command makes a commit, and tags it as a release.
|
||||||
|
The changelog looks fine, just has commits from what I can tell right now. Also has messages so works for me.
|
||||||
|
|
||||||
|
Seems to have an API integration with bb and gh so should be able to work with that easily.
|
||||||
|
|
||||||
|
Would like to implement this in sp6 for ingestion service.
|
||||||
|
|
||||||
|
I am thinking how to have this in our CI pipeline.
|
||||||
|
|
||||||
|
So in the concept of SemVer we have two public apis.
|
||||||
|
|
||||||
|
1. SNS Topic
|
||||||
|
2. KinesisFirehose
|
||||||
|
|
||||||
|
Majors - changes that are NOT back compat.
|
||||||
|
Minor - backwards compatible feature
|
||||||
|
Patch - backwards compatible fixes
|
||||||
|
|
||||||
|
So unless we make breaking changes to the output of the service ie. change the structure of the RobotMessage we are only using minor/patch.
|
||||||
|
|
||||||
|
Minors -> This will probably be mostly schema updates/ adding schema types
|
||||||
|
Patch -> This will be any bug fixes/ performance changes
|
||||||
|
|
||||||
|
The plan for a major change is to deploy another ingestion stack, release a migration guide, and push for everyone to be on it in `n` weeks.
|
||||||
|
|
||||||
|
The plan for a minor change is to release the notes.
|
||||||
|
|
||||||
|
The plan for a patch is the same as a minor.
|
||||||
|
|||||||
+1
-2
@@ -1,6 +1,6 @@
|
|||||||
[project]
|
[project]
|
||||||
name = "tagging-test"
|
name = "tagging-test"
|
||||||
version = "0.0.0"
|
version = "1.1.3"
|
||||||
description = "Add your description here"
|
description = "Add your description here"
|
||||||
readme = "README.md"
|
readme = "README.md"
|
||||||
requires-python = ">=3.13"
|
requires-python = ">=3.13"
|
||||||
@@ -26,7 +26,6 @@ prerelease_token = "rc"
|
|||||||
prerelease = false
|
prerelease = false
|
||||||
|
|
||||||
[tool.semantic_release.changelog]
|
[tool.semantic_release.changelog]
|
||||||
changelog_file = ""
|
|
||||||
exclude_commit_patterns = []
|
exclude_commit_patterns = []
|
||||||
mode = "update"
|
mode = "update"
|
||||||
insertion_flag = "<!-- version list -->"
|
insertion_flag = "<!-- version list -->"
|
||||||
|
|||||||
@@ -0,0 +1,2 @@
|
|||||||
|
This is my big feature that needs to be released.
|
||||||
|
Really big update
|
||||||
|
|||||||
Reference in New Issue
Block a user