Release v9.5.0

[lipoja]

User description

[CLOUDDST-31201]

---

PR Type

Enhancement

---

Description

• Bump version from 9.4.3 to 9.5.0 in setup.py

• Add comprehensive changelog for v9.5.0 release

• Document dependency updates and bug fixes

• Include race condition fix and file locking improvements

---

Diagram Walkthrough

flowchart LR
  A["Version 9.4.3"] -- "Release v9.5.0" --> B["Version 9.5.0"]
  B -- "Dependency Updates" --> C["Multiple Package Upgrades"]
  B -- "Bug Fixes" --> D["Race Condition & File Locking"]
  C --> E["Changelog Updated"]
  D --> E

Loading

File Walkthrough

	Relevant files
Configuration changes	setup.py Update package version to 9.5.0                                                    setup.py Update version string from 9.4.3 to 9.5.0 Reflects the new release version in package metadata +1/-1
Documentation	CHANGELOG.md Add comprehensive v9.5.0 release changelog                              CHANGELOG.md Add new v9.5.0 section with 31 changelog entries Document multiple dependency updates via renovate bot Include bug fixes: race condition avoidance and file locking improvements List requirement updates and action upgrades +31/-0

---

[sourcery-ai]

Reviewer's Guide

Prepares the project for the 9.5.0 release by adding a detailed 9.5.0 entry to the changelog and bumping the package version metadata from 9.4.3 to 9.5.0.

File-Level Changes

Change	Details	Files
Add release notes section for version 9.5.0 to the changelog.	Insert new '## 9.5.0' section under 'Unreleased' in the changelog List dependency update PRs, test infra updates, and behavioral fixes included in 9.5.0 as bullet points	CHANGELOG.md
Bump package version metadata to 9.5.0 for the new release.	Update the version field in the setup configuration from 9.4.3 to 9.5.0	setup.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `CHANGELOG.md:33` </location>
<code_context>
+* chore(deps): update dependency boto3 to v1.40.76 by @renovate[bot] in https://github.com/release-engineering/iib/pull/1247
+* chore(deps): update actions/checkout action to v6 by @renovate[bot] in https://github.com/release-engineering/iib/pull/1256
+* chore(deps): update dependency stevedore to v5.6.0 by @renovate[bot] in https://github.com/release-engineering/iib/pull/1255
+* Avoid race condition on unit-tests by @JAVGan in https://github.com/release-engineering/iib/pull/1277
+* Update requirements by @lipoja in https://github.com/release-engineering/iib/pull/1282
+* Update requirements by @lipoja in https://github.com/release-engineering/iib/pull/1286
</code_context>

<issue_to_address>
**suggestion (typo):** Consider changing "unit-tests" to "unit tests" for more standard phrasing.

This is the only bullet that hyphenates "unit tests"; updating it to "Avoid race condition on unit tests" would match the rest of the changelog and read more naturally.

```suggestion
* Avoid race condition on unit tests by @JAVGan in https://github.com/release-engineering/iib/pull/1277
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[ashwgit]

LGTM