Update default API version to 2026-04#91
Open
Firer wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps the SDK's default API version from
2026-01to2026-04(the current monday.com API version), following the established quarterly version-bump convention.Changes
lib/constants/index.ts—CURRENT_VERSION:2026-01→2026-04package.json—14.0.0→15.0.0CHANGELOG.MD— new[15.0.0]entryWhy a major bump
Changing the default
API-Versionheader is a behavior change for consumers that don't pin a version, so it's released as a major — consistent with the prior default-version bumps (11.0.0→ 2025-07,12.0.0→ 2025-10,13.0.0→ 2026-01) and with the quarterly update workflow (yarn version --new-version major).Scope notes
lib/generated/sdk.tsand@mondaydotcomorg/api-typesare produced by monday's SDK generator and, per the repo README, aren't modified in PRs. This mirrors the previous bump (6802d43), which changed only these same three files.object_relations,notetaker.meetings, document version-history queries, newExternalWidgetenum members) with no removed or renamed fields, so existing typed queries are unaffected by the new default.^\d{4}-(01|04|07|10)$check already accepts2026-04;versionOverride: '2026-04'has worked since before this PR.setup-apiunaffected. It fetches the schema withversion=current, which tracks the current version automatically.Testing
yarn build✅yarn test✅ (33/33)yarn lint✅Existing tests assert the
API-Versionheader via theDEFAULT_VERSIONconstant rather than a literal, so they continue to pass against the new default.