Skip to content

Conversation

@debdutdeb
Copy link
Member

Proposed changes (including videos or screenshots)

Issue(s)

Steps to test or reproduce

Further comments

…digit)

Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
@debdutdeb debdutdeb force-pushed the fix/houston-node-npm-version-regex branch from d60406f to 1d9395b Compare January 5, 2022 22:23
@debdutdeb debdutdeb changed the title [Fix] houston getNodeNpmVersions regex, capture whole patch [Fix] houston getNodeNpmVersions regex to capture whole patch Jan 5, 2022
@debdutdeb debdutdeb changed the title [Fix] houston getNodeNpmVersions regex to capture whole patch [FIX] houston getNodeNpmVersions regex to capture whole patch Jan 5, 2022
Copy link
Member

@sampaiodiego sampaiodiego left a comment

Choose a reason for hiding this comment

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

good catch :D

@sampaiodiego sampaiodiego changed the title [FIX] houston getNodeNpmVersions regex to capture whole patch Chore: Fix Houston getNodeNpmVersions regex to correctly get Node and Npm complete versions Jan 6, 2022
@sampaiodiego
Copy link
Member

I've updated the PR title to Chore since it's not a product fix 😉

@sampaiodiego sampaiodiego merged commit 7fc1880 into develop Jan 6, 2022
@sampaiodiego sampaiodiego deleted the fix/houston-node-npm-version-regex branch January 6, 2022 00:35
@sampaiodiego sampaiodiego mentioned this pull request Jan 29, 2022
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