Skip to content

Prepare release 1.3.1 #1030

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 26, 2025
Merged

Prepare release 1.3.1 #1030

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 10 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,15 @@
# Changelog

## securesystemslib v1.3.1

### Fixed
* AWSSigner: Don't send payload to AWS for signing, send hash only (#1026)
Copy link
Collaborator Author

@jku jku Sep 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I considered this as a simple bug fix from semver perspective: we should never have sent payloads to AWS.

* Set Development status classifier to "production/stable" in Python
packaging (#1030)

### Internals
* Minor infrastructure changes (#1005, #1013)

## securesystemslib v1.3.0

The `hash` module will be removed in the next major version. Consider using
Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ keywords = [
"ecdsa",
]
classifiers = [
"Development Status :: 4 - Beta",
"Development Status :: 5 - Production/Stable",
Copy link

@JustinCappos JustinCappos Sep 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moving to Prod / Stable makes sense given our user base seems quite stable. Any concerns from anyone? I just wanted to flag this for further comment...

Copy link
Collaborator Author

@jku jku Sep 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh right, I didn't mention that: I figured this was just forgotten since 1.0 in May 2024 was supposed to mark stability...

"Intended Audience :: Developers",
"Natural Language :: English",
"Operating System :: POSIX",
Expand Down
2 changes: 1 addition & 1 deletion securesystemslib/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import logging

__version__ = "1.3.0"
__version__ = "1.3.1"

# Configure a basic 'securesystemslib' top-level logger with a StreamHandler
# (print to console) and the WARNING log level (print messages of type
Expand Down
Loading