Bump github.com/gorilla/sessions from 1.3.0 to 1.4.0

[dependabot]

Bumps github.com/gorilla/sessions from 1.3.0 to 1.4.0.

Release notes

Sourced from github.com/gorilla/sessions's releases.

v1.4.0

Summary

There were new features important for compatibility with some of the upcoming cookie security changes with google that required a new Partitioned attribute be added to the cookies, this attribute was only available in go 1.23, which has just recently been released.

If you require a version that is backward compatible with a lower version than go 1.23 then you'll need to use release v1.3.0.

The following notes show the difference between 1.2.2 and the current version because 1.3.0 was a hotfix for go 1.22 and below.

What's Changed

• Improve File System Path Handling by @​moloch-- in gorilla/sessions#274
• #272: feat: Add support for paritioned attribute in cookies as per chrome 3rd party cookie phaseout by @​kashishbehl in gorilla/sessions#273
• fix no default samesite by @​bharat-rajani in gorilla/sessions#276
• Fix gorillatoolkit link in README.md by @​mbacalan in gorilla/sessions#278
• Add mysql store to the readme by @​danielepintore in gorilla/sessions#279

New Contributors

• @​moloch-- made their first contribution in gorilla/sessions#274
• @​kashishbehl made their first contribution in gorilla/sessions#273
• @​bharat-rajani made their first contribution in gorilla/sessions#276
• @​mbacalan made their first contribution in gorilla/sessions#278
• @​danielepintore made their first contribution in gorilla/sessions#279

Full Changelog: gorilla/sessions@v1.2.2...v1.4.0

Commits

• bb4cd60 chore: Update readme to relect go 1.23 release
• e2083f9 chore: update to go 1.23 for workflows
• 6eef180 fix: Missing SameSite attribute on options
• a56e60c Add mysql store to the readme (#279)
• 466d29e chore: Update readme and copyrights
• 7a8159e chore(go): Remove go version 1.11 support
• ff5660f chore(go): Add warning about main branch
• 8e2d547 chore(go): Remove vendored dependencies
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign vinamra28 after the PR has been reviewed.
You can assign the PR to them by writing /assign @vinamra28 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tekton-robot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pratap0007]

/retest

[tekton-robot]

@dependabot[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-tekton-hub-unit-tests	c9701b0	link	true	/test pull-tekton-hub-unit-tests
pull-tekton-hub-build-tests	c9701b0	link	true	/test pull-tekton-hub-build-tests

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.