Post release v1.3.1

[BakerNet]

No description provided.

[pooyaw]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[gemini-code-assist]

Summary of Changes

Hello @BakerNet, I'm Gemini Code Assist¹! 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 performs routine post-release maintenance. It updates a GitHub Action dependency to its latest patch version and increments the internal development version of the CLI tool, effectively preparing the codebase for the next development cycle following the v1.3.1 release.

Highlights

• GitHub Action Update: The version of the codeowners-plus GitHub Action used in the repository's workflows has been updated from v1.3.0 to v1.3.1. This ensures the project is using the latest patch release of this action.
• CLI Version Bump: The development version string for the codeowners-cli tool has been incremented from v1.3.1.dev to v1.3.2.dev. This is a standard post-release step, preparing the codebase for future development towards the next version.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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. ↩

[github-actions]

Codeowners approval required for this PR:

• @zbedforrest

[gemini-code-assist]

Code Review

This pull request updates version numbers following the v1.3.1 release. The example usage in the README is updated to v1.3.1, and the CLI's development version is bumped to v1.3.2.dev.

My review identifies two key areas for improvement:

1. A high-severity issue with the GitHub Action's versioning. The action's action.yml uses the latest Docker tag, which undermines version pinning for consumers.
2. A medium-severity maintainability issue in the CLI, where the version is hardcoded. I've suggested moving to a more robust build-time version injection using ldflags.

Addressing these points will improve the reliability and maintainability of the project.

[gemini-code-assist]

While updating the example to use the new version tag is correct, there's a significant underlying issue with how this action is versioned. The action.yml file currently points to the latest Docker image: image: 'docker://ghcr.io/multimediallc/codeowners-plus:latest'.

This means that regardless of the version specified in the uses clause (e.g., @v1.3.1), users will always execute the code from the latest Docker image. This defeats the purpose of version pinning and can lead to unexpected pipeline failures if breaking changes are introduced.

To fix this, the release process should be updated to:

1. Build and push a version-specific Docker image (e.g., ghcr.io/multimediallc/codeowners-plus:v1.3.1).
2. Update the action.yml in the corresponding git tag to point to that versioned Docker image.

This is a crucial fix for providing a stable and reliable action for your users. Since action.yml is not part of this PR, this should be addressed in a follow-up.

[gemini-code-assist]

Hardcoding the version string requires manual updates and is prone to errors. A more robust practice is to inject the version at build time using ldflags.

To implement this, you can define a package-level variable and use it here. Then, set its value during the build process.

1. Define a version variable at the package level in this file:

   var version = "dev" // Default for development builds

2. Update your build command to inject the version string:

   go build -ldflags="-X 'main.version=v1.3.2'"

This will make your release process more automated and less error-prone.

Suggested change

	Version: "v1.3.2.dev",
	Version: version,