Skip to content

feat: bump scram to 1.2.0#49338

Open
kruskall wants to merge 1 commit intoelastic:mainfrom
kruskall:feat/bump-scram
Open

feat: bump scram to 1.2.0#49338
kruskall wants to merge 1 commit intoelastic:mainfrom
kruskall:feat/bump-scram

Conversation

@kruskall
Copy link
Member

@kruskall kruskall commented Mar 7, 2026

Proposed commit message

bump scram to 1.2.0

allow project building on 1.24+ to drop custom pbkdf2 dep and use go stdlib

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
  • I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

allow project building on 1.24+ to drop custom pbkdf2 dep
and use go stdlib
@kruskall kruskall requested a review from a team as a code owner March 7, 2026 02:10
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 7, 2026
@botelastic
Copy link

botelastic bot commented Mar 7, 2026

This pull request doesn't have a Team:<team> label.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 7, 2026

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@mergify
Copy link
Contributor

mergify bot commented Mar 7, 2026

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kruskall? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@coderabbitai
Copy link

coderabbitai bot commented Mar 7, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 4cdceab8-9c96-4105-81f5-2e40ee96b7f0

📥 Commits

Reviewing files that changed from the base of the PR and between 7c1607e and 0c81737.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (2)
  • NOTICE.txt
  • go.mod

📝 Walkthrough

Walkthrough

Updated the xdg-go/scram dependency from v1.1.2 to v1.2.0 in go.mod. Corresponding updates were made to NOTICE.txt to reflect the new version and its associated license file path. No functional code or logic changes were introduced.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • 🛠️ Update Documentation: Commit on current branch
  • 🛠️ Update Documentation: Create PR

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement needs_team Indicates that the issue/PR needs a Team:* label skip-changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants