8000
Skip to content

chore(main): release 4.4.0 - #3145

Merged
jooola merged 2 commits into
mainfrom
release-please--branches--main--components--libretime
May 29, 2025
Merged

chore(main): release 4.4.0#3145
jooola merged 2 commits into
mainfrom
release-please--branches--main--components--libretime

Conversation

@libretime-bot
@libretime-bot libretime-bot commented Mar 18, 2025
Copy link
Copy Markdown
Collaborator

🤖 I have created a release beep boop

4.4.0 (2025-05-29)

Features

  • build and run custom nginx container (#3155) (658ce15)
  • include nginx config inside libretime-nginx container (#3157) (659ac7a)

Bug Fixes

  • legacy: now macro should use station timezone (#3143) (c554863)
  • legacy: scheduled show length should not add track fade times (#3144) (5743a0f)

This PR was generated with Release Please. See documentation.

@libretime-bot
libretime-bot force-pushed the release-please--branches--main--components--libretime branch 2 times, most recently from 86776df to bb12d53 Compare March 21, 2025 10:55
@libretime-bot
libretime-bot force-pushed the release-please--branches--main--components--libretime branch 2 times, most recently from 486fd04 to d16861e Compare April 14, 2025 09:55
@libretime-bot libretime-bot changed the title chore(main): release 4.3.1 chore(main): release 4.4.0 May 29, 2025
@libretime-bot
libretime-bot force-pushed the release-please--branches--main--components--libretime branch from d16861e to 3a447fe Compare May 29, 2025 15:04
@paddatrapper
Copy link
Copy Markdown
Contributor

A note that the release notes for this release need to include how to update docker-based setups to use the new custom nginx image

@jooola
jooola commented May 29, 2025
Copy link
Copy Markdown
Contributor

Should we cut a release? I am already using your fix, and don't mind a new version :)

@paddatrapper
Copy link
Copy Markdown
Contributor

My only question is if we want to include #3149 and the testing that goes along with it?

@jooola
jooola commented May 29, 2025
Copy link
Copy Markdown
Contributor

I do not think 3149 is ready, so I'd rather not try to squeeze it in a release.

(Either the PR scope is too wide, or changes are missing)

@paddatrapper
Copy link
Copy Markdown
Contributor

Then I'm happy for us to release v4.4.0 as things stand

@libretime-bot
libretime-bot force-pushed the release-please--branches--main--components--libretime branch from 3a447fe to f639100 Compare May 29, 2025 18:58
@jooola
jooola merged commit ef1b6f1 into main May 29, 2025
@jooola
jooola deleted the release-please--branches--main--components--libretime branch May 29, 2025 19:16
@libretime-bot
Copy link
Copy Markdown
Collaborator Author

🤖 Created releases:

🌻

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.

3 participants

0