Skip to content

fix: clean up earlier refactor issues with maxExtensionTime#2127

Merged
feywind merged 1 commit intomainfrom
gh-2054-maxextensiontime
Feb 11, 2026
Merged

fix: clean up earlier refactor issues with maxExtensionTime#2127
feywind merged 1 commit intomainfrom
gh-2054-maxextensiontime

Conversation

@feywind
Copy link
Collaborator

@feywind feywind commented Feb 10, 2026

The maxExtensionTime field was not being carried over into Subscriber, from a refactor a while back of various settings. This fixes that and adds a unit test for it.

This also patches out an old/faulty bit of documentation about maxExtensionMinutes.

Fixes #2054 🦕

@feywind feywind requested review from a team as code owners February 10, 2026 23:15
@product-auto-label product-auto-label bot added size: s Pull request size is small. api: pubsub Issues related to the googleapis/nodejs-pubsub API. labels Feb 10, 2026
@feywind feywind added the owlbot:run Add this label to trigger the Owlbot post processor. label Feb 10, 2026
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Feb 10, 2026
Copy link

@quirogas quirogas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

@feywind feywind merged commit c22471d into main Feb 11, 2026
21 checks passed
@feywind feywind deleted the gh-2054-maxextensiontime branch February 11, 2026 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: pubsub Issues related to the googleapis/nodejs-pubsub API. size: s Pull request size is small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐞 Bug: maxExtensionTime Ignored in Subscription Constructor

2 participants