[MehdiZare]

Dependency maintenance; no separate tracking issue.

Before the change?

The latest published provider binary produced 32 advisory matches in govulncheck v1.9.0 -mode=binary. These are binary-symbol matches, not a claim that every advisory is exploitable through provider operations.

This updates the build toolchain and affected modules, and adds a binary scan for Linux AMD64 and macOS ARM64. Both rebuilt targets report No vulnerabilities found. Provider schemas and Terraform validation results for omitted and explicit-null optional configuration match the unchanged source baseline.

Validation: before/after offline unit tests pass; module tidy and whitespace checks pass; workflow checked with actionlint. Live service acceptance was not run. Maintainers still need to validate their release process and publish a new signed version; existing registry artifacts are unchanged.

Configured golangci-lint checks pass with v2.15.0.

After the change?

CI builds use Go 1.27.2, while the language minimum stays on patched Go 1.26.9. Two JWT test log statements now format numeric dates correctly under current vet checks. No resource schema changes.

Pull request checklist

• Schema migrations reviewed: not needed.
• Added compiled-binary security checks and ran existing offline tests.
• Documentation reviewed: no resource/API behavior change.

Does this introduce a breaking change?

• Yes, for source builders requiring Go older than 1.26.9; CI selects Go 1.27.2. No intended Terraform configuration break.
• No

AI-assisted contribution prepared and tested with Codex. Live GitHub acceptance remains unverified.

[github-actions]

👋 Hi, and thank you for this contribution!

This repo is maintained by GitHub and community members on a best-effort basis. We'll get to this as soon as we can.

You can help us prioritize by joining the discussion on open issues and PRs, sharing details on the changes you need, and reviewing other contributions.

---

_{🤖 This is an automated message.}