Skip to content

Fix monorepo npm release, bring in incompatible nodenext timestamp fn #16

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

Jump to bottom
Merged
rosskevin merged 6 commits into from
Jan 22, 2025
Merged

Fix monorepo npm release, bring in incompatible nodenext timestamp fn #16

rosskevin merged 6 commits into from
Jan 22, 2025

Conversation

@rosskevin
Copy link
Member

@rosskevin rosskevin commented Jan 22, 2025 •
edited
Loading

📦 Published PR as canary version: 11.0.32--canary.16.663d9f5.0

✨ Test out this PR locally via:

npm install @alienfast/[email protected]
npm install @alienfast/[email protected]
npm install @alienfast/[email protected]
# or 
yarn add @alienfast/[email protected]
yarn add @alienfast/[email protected]
yarn add @alienfast/[email protected]

@rosskevin
use lerna for additional npm release, add verification via tsc, bring…
7850c92 
… in timestamp fn that was incompatible with nodenext
@rosskevin rosskevin changed the title use lerna for additional npm release, add verification via tsc, bring… Fix monorepo npm release, bring in incompatible nodenext timestamp fn Jan 22, 2025
@rosskevin rosskevin merged commit f10faca into main Jan 22, 2025
1 check passed
@rosskevin rosskevin deleted the fix-monorepo-release branch January 22, 2025 21:57
@rosskevin
Copy link
Member Author

rosskevin commented Jan 22, 2025

🚀 PR was released in v11.0.32 🚀

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

Reviewers

No reviews

Assignees

No one assigned

Labels

released

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@rosskevin