Skip to content
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.

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

release: v1.5.0 #434

Merged
merged 1 commit into from
Dec 10, 2024
Merged

Conversation

openui5bot
Copy link
Contributor

@openui5bot openui5bot commented Dec 3, 2024

🚜 New release prepared

1.5.0 (2024-12-10)

Features

  • Add ruleId to Markdown format output (913007c)
  • Detect override of control "rerender" (f416a0c)

Bug Fixes

  • Detect deprecations in new expressions with ID (156e747)
  • Detect more deprecated renderer declarations (74f65bf)
  • Improve module resolution (ce4eed8)
  • Match ignore-pattern starting with "./" (4eb2758)

Dependencies

  • Bump @sapui5/types to 1.120.24 (d0760c9)

This PR was generated with Release Please. See documentation.

@openui5bot openui5bot force-pushed the release-please--branches--main--components--linter branch 2 times, most recently from 26737ab to faede43 Compare December 5, 2024 08:59
@openui5bot openui5bot changed the title release: v1.4.2 release: v1.5.0 Dec 6, 2024
@openui5bot openui5bot force-pushed the release-please--branches--main--components--linter branch 4 times, most recently from 25e6d03 to 4fa2a91 Compare December 9, 2024 15:31
@openui5bot openui5bot force-pushed the release-please--branches--main--components--linter branch from 4fa2a91 to be246c5 Compare December 10, 2024 08:14
@matz3 matz3 merged commit 09141c0 into main Dec 10, 2024
13 checks passed
@matz3 matz3 deleted the release-please--branches--main--components--linter branch December 10, 2024 10:55
@openui5bot
Copy link
Contributor Author

🤖 Release is at https://github.com/SAP/ui5-linter/releases/tag/v1.5.0 🌻

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

Successfully merging this pull request may close these issues.

2 participants