Skip to content

Updated to work with Node versions 18 through 26 - #17

Open
Dan-Berk-AYX wants to merge 9 commits into
mainfrom
Update-Node-18-Through-26
Open

Updated to work with Node versions 18 through 26#17
Dan-Berk-AYX wants to merge 9 commits into
mainfrom
Update-Node-18-Through-26

Conversation

@Dan-Berk-AYX

@Dan-Berk-AYX Dan-Berk-AYX commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

License

By contributing your code to the alteryx/react-comms GitHub repository, you agree to license your contribution under the MIT license.

  • I have read the above statement and am aware that I am making contributions to an open source project and that contribution is being licensed under the MIT License.

@Dan-Berk-AYX Dan-Berk-AYX self-assigned this Aug 5, 2026
Comment thread .gitlab-ci.yml Outdated
Comment thread .gitlab-ci.yml Outdated
@Dan-Berk-AYX
Dan-Berk-AYX requested a review from RezaAkhtar August 6, 2026 16:16
{
"name": "@alteryx/react-comms",
"version": "1.0.1",
"version": "1.0.2",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Revert the version change. Let's separate the Node version compatibility change from the version bump, and instead create a "Release PR" where we can bundle the version bump and a CHANGELOG entry together. Merging that PR will be the trigger for the tag and release.

Worth folding into the 1.0.2 changelog: main already has 3 commits since v1.0.1 that never got a release:

  • #13 (boolean conversion docs example),
  • a babel warning fix, and
  • the PR template addition.

None of those are in any changelog entry currently.

Given the severity of the changes, we should also bump the minor rather than the patch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants