Skip to content

release: UI5 CLI packages main #1198

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
d3xter666 merged 1 commit into from
Dec 2, 2025
Merged

release: UI5 CLI packages main #1198

d3xter666 merged 1 commit into from
Dec 2, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Nov 18, 2025 •
edited by d3xter666
Loading

🚜 New release prepared

builder: 5.0.0-alpha.0

5.0.0-alpha.0 (2025-12-02)

Breaking Changes

  • builder: Require Node.js 22.20.0 || >= 24.0.0

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @ui5/fs bumped from ^4.0.2 to ^5.0.0-alpha.0
      • @ui5/logger bumped from ^4.0.2 to ^5.0.0-alpha.0
    • devDependencies
      • @ui5/project bumped from ^4.0.6 to ^5.0.0-alpha.0
cli: 5.0.0-alpha.0

5.0.0-alpha.0 (2025-12-02)

Breaking Changes

  • cli: Require Node.js 22.20.0 || >= 24.0.0
  • cli: Default to Specification Version 5.0 in ui5 init (c1b1432)

Features

  • cli: Use specVersion 5.0 in init command (c1b1432)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @ui5/builder bumped from ^4.0.11 to ^5.0.0-alpha.0
      • @ui5/fs bumped from ^4.0.2 to ^5.0.0-alpha.0
      • @ui5/logger bumped from ^4.0.2 to ^5.0.0-alpha.0
      • @ui5/project bumped from ^4.0.6 to ^5.0.0-alpha.0
      • @ui5/server bumped from ^4.0.7 to ^5.0.0-alpha.0
fs: 5.0.0-alpha.0

5.0.0-alpha.0 (2025-12-02)

Breaking Changes

  • fs: Require Node.js 22.20.0 || >= 24.0.0

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @ui5/logger bumped from ^4.0.2 to ^5.0.0-alpha.0
logger: 5.0.0-alpha.0

5.0.0-alpha.0 (2025-12-02)

Breaking Changes

  • logger: Require Node.js 22.20.0 || >= 24.0.0

Features

  • logger: Add module filtering, task-skip event (5a1b071)
project: 5.0.0-alpha.0

5.0.0-alpha.0 (2025-12-02)

Breaking Changes

  • project: Require Node.js 22.20.0 || >= 24.0.0

Features

  • project: Add component type (46eb4e4)
  • project: Add Specification Version 5.0 (1452401)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @ui5/fs bumped from ^4.0.2 to ^5.0.0-alpha.0
      • @ui5/logger bumped from ^4.0.2 to ^5.0.0-alpha.0
    • peerDependencies
      • @ui5/builder bumped from ^4.0.11 to ^5.0.0-alpha.0
server: 5.0.0-alpha.0

5.0.0-alpha.0 (2025-12-02)

Breaking Changes

  • server: Require Node.js 22.20.0 || >= 24.0.0

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @ui5/builder bumped from ^4.0.11 to ^5.0.0-alpha.0
      • @ui5/fs bumped from ^4.0.2 to ^5.0.0-alpha.0
      • @ui5/logger bumped from ^4.0.2 to ^5.0.0-alpha.0
    • devDependencies
      • @ui5/project bumped from ^4.0.6 to ^5.0.0-alpha.0

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main branch 6 times, most recently from a9292c5 to 52868a6 Compare November 25, 2025 09:01
@d3xter666 d3xter666 force-pushed the release-please--branches--main branch from e06957b to 7b5c4cf Compare November 25, 2025 12:17
@github-actions github-actions bot force-pushed the release-please--branches--main branch 3 times, most recently from c3a5ab6 to 32e9342 Compare November 26, 2025 07:45
@d3xter666 d3xter666 force-pushed the release-please--branches--main branch from 32e9342 to f68b19c Compare November 26, 2025 13:45
@github-actions github-actions bot force-pushed the release-please--branches--main branch from f68b19c to 74e5638 Compare November 27, 2025 09:11
@github-actions github-actions bot changed the title release: UI5 CLI packages release: UI5 CLI packages main Nov 27, 2025
@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from 67129ee to 806774d Compare November 27, 2025 13:08
@d3xter666 d3xter666 force-pushed the release-please--branches--main branch from 806774d to cd5cc1b Compare November 27, 2025 13:29
@d3xter666 d3xter666 requested a review from a team November 27, 2025 13:32
@coveralls
Copy link

coveralls commented Nov 27, 2025 •
edited
Loading

Coverage Status

coverage: 94.657% (-0.03%) from 94.69%
when pulling 34dfd68 on release-please--branches--main
into 60d176d on main.

@d3xter666 d3xter666 force-pushed the release-please--branches--main branch from cd5cc1b to e8e260e Compare November 27, 2025 14:08
@RandomByte
Copy link
Member

RandomByte commented Nov 27, 2025

Why is the change in package-lock.json so huge? I wouldn't expect any changes during release. Could this be caused by this line?

cli/.github/workflows/release-please.yml

Lines 45 to 46 in 2ff8c59

# Regenerate package-lock.json to sync with updated workspace packages
npm install

@github-actions github-actions bot force-pushed the release-please--branches--main branch 6 times, most recently from 8064b8c to 7d44afb Compare November 28, 2025 09:40
@d3xter666 d3xter666 force-pushed the release-please--branches--main branch from 7d44afb to bc570a5 Compare November 28, 2025 12:00
@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from dfe42f2 to 8456e0c Compare November 28, 2025 13:37
RandomByte
RandomByte requested changes Dec 1, 2025
View reviewed changes
@github-actions github-actions bot force-pushed the release-please--branches--main branch 10 times, most recently from a69f98f to 3e9cd51 Compare December 2, 2025 10:02
@d3xter666 d3xter666 force-pushed the release-please--branches--main branch from 3e9cd51 to 82ea8f1 Compare December 2, 2025 11:07
@d3xter666 d3xter666 requested a review from a team December 2, 2025 11:56
@d3xter666
Copy link
Member

d3xter666 commented Dec 2, 2025

Why is the change in package-lock.json so huge? I wouldn't expect any changes during release. Could this be caused by this line?

cli/.github/workflows/release-please.yml

Lines 45 to 46 in 2ff8c59

# Regenerate package-lock.json to sync with updated workspace packages
npm install

Thanks to da120c7 this is not the case anymore

matz3
matz3 reviewed Dec 2, 2025
View reviewed changes
Copy link
Member

@matz3 matz3 left a comment

Choose a reason for hiding this comment

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

LGTM otherwise

@d3xter666 d3xter666 force-pushed the release-please--branches--main branch from 82ea8f1 to dde178b Compare December 2, 2025 12:16
RandomByte
RandomByte previously approved these changes Dec 2, 2025
View reviewed changes
@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from a1afe92 to 4c373c8 Compare December 2, 2025 12:44
@d3xter666 d3xter666 force-pushed the release-please--branches--main branch from 4c373c8 to 34dfd68 Compare December 2, 2025 13:25
@d3xter666 d3xter666 requested review from RandomByte and matz3 December 2, 2025 13:33
@d3xter666 d3xter666 merged commit 76fbae6 into main Dec 2, 2025
30 checks passed
@d3xter666 d3xter666 deleted the release-please--branches--main branch December 2, 2025 13:49
@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 2, 2025

🤖 Created releases:

🌻

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

Reviewers

@d3xter666 d3xter666 d3xter666 left review comments

@RandomByte RandomByte RandomByte approved these changes

@matz3 matz3 Awaiting requested review from matz3

Assignees

No one assigned

Labels

autorelease: tagged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@coveralls @RandomByte @d3xter666 @matz3