Skip to content

fix: updating web-sdk-types version #516

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ifefamojuro merged 2 commits into from
Jan 9, 2026
Merged

fix: updating web-sdk-types version #516

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1b2b4f6
types package on package.json
ifefamojuro Jan 8, 2026
3eb85da
update to 1.81.1
ifefamojuro Jan 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,6 @@
]
},
"dependencies": {
"@square/web-payments-sdk-types": "^1.79.0"
"@square/web-payments-sdk-types": "^1.81.1"
Copy link
Contributor

@sirianil sirianil Jan 8, 2026

Choose a reason for hiding this comment

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

why do we need to do this manually?

Copy link
Contributor Author

@ifefamojuro ifefamojuro Jan 8, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

This package uses npm/npx based package controls, rather than the yarn + yarn upgrade-interactive that we are used to

Copy link
Contributor

@nwilmessquare nwilmessquare Jan 9, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

We normally see types version updates as dependabot PRs. In fact, I see one open right now (PR #503)

Copy link
Contributor Author

@ifefamojuro ifefamojuro Jan 9, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

I wanted to test our new NPM key, by prompting the release of a new package version. According to the runbooks, the best way to do this is with a fix pr (ex. here)

Copy link
Contributor

@nwilmessquare nwilmessquare Jan 9, 2026

Choose a reason for hiding this comment

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

Got it, makes sense.

}
}