Skip to content

docs: add changelog for v1.1.2#2220

Open
cozystack-bot wants to merge 1 commit intomainfrom
changelog-v1.1.2
Open

docs: add changelog for v1.1.2#2220
cozystack-bot wants to merge 1 commit intomainfrom
changelog-v1.1.2

Conversation

@cozystack-bot
Copy link
Member

@cozystack-bot cozystack-bot commented Mar 13, 2026

This PR adds the changelog for release v1.1.2.

✅ Changelog has been automatically generated in docs/changelogs/v1.1.2.md.

Summary by CodeRabbit

  • Bug Fixes

    • Fixed S3 endpoint resolution issue that caused invalid credentials errors.
    • Resolved spurious OpenAPI post-processing errors.
  • Documentation

    • Updated multiple guides covering installation, deployment, operations, and architecture.
    • Added contributor acknowledgments.

@cozystack-bot cozystack-bot added automated documentation Improvements or additions to documentation labels Mar 13, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces the official changelog for the v1.1.2 release of Cozystack. It meticulously documents several key bug fixes related to S3 Manager login and OpenAPI schema processing, alongside significant updates and additions to the project's documentation, covering installation, troubleshooting, metrics, architecture, and backup procedures. The changes aim to enhance user experience, clarify operational workflows, and provide better guidance for platform users and operators.

Highlights

  • Fixes: Resolved an S3 Manager login endpoint mismatch when using COSI-issued credentials, ensuring reliable logins by correctly resolving the endpoint from BucketInfo.
  • Fixes: Addressed spurious OpenAPI schema errors that occurred for non-application group versions during cozystack-api startup, reducing log noise.
  • Documentation: Added a comprehensive guide for automated Cozystack deployment using the cozystack.installer Ansible collection.
  • Documentation: Clarified the operator-first installation flow in the platform guide and tutorial, aligning with the supported workflow.
  • Documentation: Provided new troubleshooting guidance for packages stuck in DependenciesNotReady and fixed an outdated make target reference.
  • Documentation: Documented how tenants can expose custom Prometheus exporters using VMServiceScrape and VMPodScrape.
  • Documentation: Expanded Key Concepts documentation to detail the PackageSource and Package reconciliation model, dependency handling, and update mechanisms.
  • Documentation: Improved the Velero backup and recovery operations guide with clearer examples, verification steps, and operational commands.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • docs/changelogs/v1.1.2.md
    • Added a new changelog file for version v1.1.2.
    • Included a 'Fixes' section detailing resolutions for S3 Manager login endpoint mismatches and OpenAPI schema errors.
    • Incorporated a 'Documentation' section with updates on Ansible installation, operator-first flow, troubleshooting, custom metrics, Package architecture, and improved backup guides.
    • Listed contributors to the v1.1.2 release.
Activity
  • The changelog for release v1.1.2 has been automatically generated and added to docs/changelogs/v1.1.2.md.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 13, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1500f216-e42d-4a7a-a5f6-04e53278e8b8

📥 Commits

Reviewing files that changed from the base of the PR and between 8e62d4c and 4b250a2.

📒 Files selected for processing (1)
  • docs/changelogs/v1.1.2.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/changelogs/v1.1.2.md

📝 Walkthrough

Walkthrough

Adds docs/changelogs/v1.1.2.md containing v1.1.2 release notes: fixes for OpenAPI post-processing (early exit when base Application schemas are absent), S3 BucketInfo endpoint extraction with first-deploy fallback, many documentation guide additions, and contributor acknowledgments.

Changes

Cohort / File(s) Summary
Changelog Release
docs/changelogs/v1.1.2.md
Adds v1.1.2 release notes describing fixes for OpenAPI post-processing and BucketInfo S3 endpoint extraction/fallback, numerous documentation and guide updates (installation, troubleshooting, CA rotation, backup/recovery, metrics, packaging), and contributor acknowledgments.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

size:S

Suggested reviewers

  • kvaps
  • lllamnyp
  • lexfrei
  • androndo
  • IvanHunters
  • sircthulhu

Poem

🐰 I hopped in to mark the news,
A changelog bright with fixes and clues,
Endpoints and schemas aligned,
Docs polished, clear, and kind,
Cheers for v1.1.2 — hop, ooh! 🎉

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: add changelog for v1.1.2' directly and clearly describes the main change: adding a changelog document for version 1.1.2.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch changelog-v1.1.2
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/changelogs/v1.1.2.md`:
- Around line 25-37: The commit that added docs/changelogs/v1.1.2.md uses "docs:
add changelog for v1.1.2" instead of the required bracketed component format;
amend the commit message to "[docs] add changelog for v1.1.2" (preserving the
existing Signed-off-by trailer) by running an interactive amend (e.g., git
commit --amend with the corrected subject) and, if the commit was already
pushed, force-push the updated commit to the branch (git push
--force-with-lease) so the repo follows the `**/*.md` `[component] Description`
guideline.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c2851783-ebdd-4996-8761-db708794145f

📥 Commits

Reviewing files that changed from the base of the PR and between ffd6e62 and ab2772e.

📒 Files selected for processing (1)
  • docs/changelogs/v1.1.2.md

Comment on lines +25 to +37
## Contributors

We'd like to thank all contributors who made this release possible:

* [**@androndo**](https://github.com/androndo)
* [**@IvanHunters**](https://github.com/IvanHunters)
* [**@kvaps**](https://github.com/kvaps)
* [**@lexfrei**](https://github.com/lexfrei)
* [**@sircthulhu**](https://github.com/sircthulhu)

---

**Full Changelog**: https://github.com/cozystack/cozystack/compare/v1.1.1...v1.1.2
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Show commits that touched this file (subject + body)
git log --pretty=format:'COMMIT %H%nSUBJECT: %s%nBODY:%n%b%n----' -- docs/changelogs/v1.1.2.md

# Quick check for expected subject prefix pattern and Signed-off-by trailer
git log --pretty=format:'%H%x09%s%x09%b' -- docs/changelogs/v1.1.2.md | \
awk -F'\t' '
{
  commit=$1; subject=$2; body=$3;
  subject_ok = (subject ~ /^\[[^]]+\] .+/);
  signoff_ok = (body ~ /Signed-off-by:[[:space:]]+/);
  printf "%s | subject_ok=%s | signoff_ok=%s\n", commit, subject_ok?"yes":"no", signoff_ok?"yes":"no";
}'

Repository: cozystack/cozystack

Length of output: 315


Commit subject does not follow the required [component] Description format.

The file content is well-structured, but the commit that introduced this change uses docs: add changelog for v1.1.2 instead of the required [docs] add changelog for v1.1.2 (square brackets required around the component). The Signed-off-by trailer is correctly present. Amend the commit message to comply with the **/*.md guideline: [component] Description format.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/changelogs/v1.1.2.md` around lines 25 - 37, The commit that added
docs/changelogs/v1.1.2.md uses "docs: add changelog for v1.1.2" instead of the
required bracketed component format; amend the commit message to "[docs] add
changelog for v1.1.2" (preserving the existing Signed-off-by trailer) by running
an interactive amend (e.g., git commit --amend with the corrected subject) and,
if the commit was already pushed, force-push the updated commit to the branch
(git push --force-with-lease) so the repo follows the `**/*.md` `[component]
Description` guideline.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces the changelog for the upcoming v1.1.2 release. The new file, docs/changelogs/v1.1.2.md, is well-structured and clearly documents the fixes and documentation improvements. The content appears to be automatically generated and is consistent in its formatting. After a thorough review, I found no issues with the content, formatting, or accuracy of the changelog based on the provided context.

@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Mar 13, 2026
Signed-off-by: cozystack-bot <217169706+cozystack-bot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated documentation Improvements or additions to documentation size:M This PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant