Auto release fix

[goruha]

What

• Use auto relesase shared workflow

Why

• https://cloudposse.atlassian.net/browse/DEV-1747

[coderabbitai]

Walkthrough

This update introduces a new configuration file for repository settings and modifies the automated release workflow. The newly added .github/settings.yml file allows for the customization of repository settings, including the project's homepage URL and the enablement of projects and wikis. Meanwhile, the release process has been streamlined by replacing the publish job in .github/workflows/auto-release.yml with an auto job, utilizing a different action to manage releases more efficiently.

Changes

Files	Change Summary
.github/settings.yml	Adds a new file to configure repository settings like homepage URL and project/wiki enablement.
.github/.../auto-release.yml	Replaces publish job with auto job using a different action for release management.

🐇✨
In the burrow of the code, a new file takes abode,
Settings tuned with care, a repository's flair.
With a hop and a skip, the release process flips,
An 'auto' job in place, releases race with grace.
🌟📦🚀

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between f3f47ba and 2e6718d.

Files selected for processing (2)

• .github/settings.yml (1 hunks)
• .github/workflows/auto-release.yml (1 hunks)

Additional comments: 2

.github/workflows/auto-release.yml (1)

• 9-13: The introduction of the auto job using a shared workflow is a significant change aimed at automating the release process. Ensure that:

• The referenced shared workflow (cloudposse/.github/.github/workflows/shared-auto-release.yml@main) exists and is accessible.
• The publish: true parameter aligns with the intended behavior of automatically publishing releases.
• Inheriting secrets does not violate any security policies or guidelines within your organization.

Verification successful

---

The shared workflow cloudposse/.github/.github/workflows/shared-auto-release.yml@main has been confirmed to exist and is accessible. However, the verification of the publish: true parameter's alignment with intended behavior and the security implications of inheriting secrets requires further review within the context of your organization's policies and the shared workflow's documentation or source code.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify the existence of the shared workflow
curl -fsSL https://github.com/cloudposse/.github/blob/main/.github/workflows/shared-auto-release.yml > /dev/null
if [ $? -ne 0 ]; then
  echo "The shared workflow does not exist or is not accessible."
else
  echo "The shared workflow exists and is accessible."
fi

Length of output: 221

.github/settings.yml (1)

• 1-13: The settings file introduces several configurations for the repository:

• Extending cloudposse/.github for shared settings is a good practice for consistency.
• The homepage URL (https://cloudposse.com) should be verified to ensure it's the correct link for the repository's documentation or landing page.
• Disabling projects (has_projects: false) and wikis (has_wiki: false) should align with the project's management strategy. Confirm that these settings are intentional and reflect the project's needs.

Verification successful

---

The homepage URL (https://cloudposse.com) has been verified as accessible, aligning with the settings specified in the .github/settings.yml file. The other configurations, including the disabling of projects and wikis, should align with the project's management strategy and are assumed to be intentional based on the review context.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify the homepage URL is correct
curl -fsSL https://cloudposse.com > /dev/null
if [ $? -ne 0 ]; then
  echo "The homepage URL does not seem to be correct or is not accessible."
else
  echo "The homepage URL is accessible."
fi

Length of output: 126

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 2e6718d and 704d623.

Files selected for processing (1)

• .github/workflows/auto-release.yml (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/auto-release.yml