Compare commits

..

10 Commits

Author SHA1 Message Date
Alex Muszynski 606fc8d4e6 docs(readme): updated thoughts 2025-06-07 18:50:34 -04:00
semantic-release 4ee0f5c7b1 1.1.3
Automatically generated by python-semantic-release
2025-06-07 18:31:47 -04:00
Alex Muszynski cb061287cd fix(readme): non critical issue, but still an issue 2025-06-07 18:30:39 -04:00
semantic-release 601227c97b 1.1.2
Automatically generated by python-semantic-release
2025-06-07 18:26:40 -04:00
semantic-release ba1977422e 1.1.1
Automatically generated by python-semantic-release
2025-06-07 18:26:28 -04:00
semantic-release 16db7e0a7f 1.1.0
Automatically generated by python-semantic-release
2025-06-07 18:24:53 -04:00
Alex Muszynski ce62257c51 feat(apis): really big update 2025-06-07 18:24:39 -04:00
semantic-release 316579c812 1.0.0
Automatically generated by python-semantic-release
2025-06-07 18:23:22 -04:00
Alex Muszynski 0922d51dce chore(config): configure Python Semantic Release 2025-06-07 18:23:17 -04:00
Alex Muszynski 6c12d22cce feat: massive user facing feature 2025-06-07 18:06:24 -04:00
4 changed files with 62 additions and 2 deletions
+29
View File
@@ -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
+30
View File
@@ -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
View File
@@ -1,6 +1,6 @@
[project]
name = "tagging-test"
version = "0.0.0"
version = "1.1.3"
description = "Add your description here"
readme = "README.md"
requires-python = ">=3.13"
@@ -26,7 +26,6 @@ prerelease_token = "rc"
prerelease = false
[tool.semantic_release.changelog]
changelog_file = ""
exclude_commit_patterns = []
mode = "update"
insertion_flag = "<!-- version list -->"
+2
View File
@@ -0,0 +1,2 @@
This is my big feature that needs to be released.
Really big update