Upgrade baton-sdk to v0.2.49.

[ggreer]

This improves grant expansion performance.

Summary by CodeRabbit

• Chores
  • Updated the version of the github.com/conductorone/baton-sdk dependency.

[coderabbitai]

Walkthrough

The pull request involves a single change to the go.mod file, specifically updating the version of the github.com/conductorone/baton-sdk dependency from v0.2.48 to v0.2.49. No other dependencies are affected, and there are no changes to other files or sections.

Changes

File	Change Summary
go.mod	Updated github.com/conductorone/baton-sdk from v0.2.48 to v0.2.49 in the require section.

Possibly related PRs

• Upgrade baton-sdk to v0.2.46. #42: This PR also updates the version of the github.com/conductorone/baton-sdk dependency in the go.mod file, making it directly related to the version change in the main PR.

🐰 In the meadow, hops a little hare,
Updating versions with utmost care.
From v0.2.48 to v0.2.49,
A leap of progress, oh so fine!
With each small change, we dance and play,
In the world of code, we hop away! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7b4559a and 330810d.

⛔ Files ignored due to path filters (4)

• go.sum is excluded by !**/*.sum and included by none
• vendor/github.com/conductorone/baton-sdk/pkg/dotc1z/grants.go is excluded by !vendor/** and included by none
• vendor/github.com/conductorone/baton-sdk/pkg/sdk/version.go is excluded by !vendor/** and included by none
• vendor/modules.txt is excluded by !vendor/** and included by none

📒 Files selected for processing (1)

• go.mod (1 hunks)

🔇 Additional comments (2)

go.mod (2)

6-6: LGTM! Verify changelog for breaking changes.

The update from v0.2.48 to v0.2.49 matches the PR objectives for enhancing grant expansion performance.

Let's verify the version and check for any breaking changes:

✅ Verification successful

✅ Safe to proceed with the update

The verification confirms:

• v0.2.49 is the latest released version
• Changes between v0.2.48 and v0.2.49 focus on performance optimization:
  • Added index on entitlement + principal to improve grant expansion speed
  • No breaking changes introduced

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the latest version and changelog for baton-sdk

# Check the latest version
gh api repos/conductorone/baton-sdk/releases/latest --jq .tag_name

# Get the changelog between versions
gh api repos/conductorone/baton-sdk/compare/v0.2.48...v0.2.49 --jq '.commits[].commit.message'

Length of output: 276

---

Line range hint 10-99: Verify indirect dependency changes.

Let's ensure the SDK update hasn't introduced any problematic indirect dependency changes.

✅ Verification successful

No concerning changes in indirect dependencies

The diff shows that this is a minor version bump of the baton-sdk from v0.2.48 to v0.2.49. All other dependencies remain unchanged, indicating that this update hasn't introduced any new indirect dependencies or security-sensitive changes.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Compare indirect dependencies before and after the update

# Create temporary go.mod files
echo "module test
go 1.22.2
require github.com/conductorone/baton-sdk v0.2.48" > old.mod

echo "module test
go 1.22.2
require github.com/conductorone/baton-sdk v0.2.49" > new.mod

# Compare dependencies
go mod tidy -modfile=old.mod
go mod tidy -modfile=new.mod
diff <(go list -m -modfile=old.mod all) <(go list -m -modfile=new.mod all)

# Clean up
rm old.mod new.mod

Length of output: 807

---

Script:

#!/bin/bash
# Let's try a different approach by examining the git history of go.mod
git show HEAD^:go.mod > old_mod.txt
git show HEAD:go.mod > new_mod.txt
diff old_mod.txt new_mod.txt
rm old_mod.txt new_mod.txt

Length of output: 206

---

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>, please review it.
  • Generate unit testing code 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.