Skip to content

Conversation

jelledijkstra97
Copy link
Collaborator

Description

What have you changed and why?

Type of change

(Remove irrelevant options)

  • Minor change (typo, formatting, version bump)
  • New feature
  • Improvement of existing feature
  • Bugfix
  • Refactoring
  • Configuration change
  • Breaking change

Checklist:

  • I've double-checked the code in this PR myself
  • I've left the code better than before (boy scout rule)
  • The code is readable, comments are added that explain hard or non-obvious parts.
  • I've expanded/improved the (unit) tests, when applicable
  • I've run (unit) tests that prove my solution works
  • There's no sensitive information like credentials in my PR

@rkettelerij
Copy link
Collaborator

Is dit wel een upgrade naar lighthttp 1.5.0? https://github.com/PDOK/lighttpd-docker/releases/tag/1.5.0 bestaat (alleen tag, geen release) maar daarin is het lighttpd versienummer niet verhoogd....

Copy link
Collaborator

@rkettelerij rkettelerij left a comment

Choose a reason for hiding this comment

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

Of ging het alleen om de debian upgrade? Het versienummer houden we namelijk gelijk aan het versienummer van lighthttpd

@Daimanta Daimanta merged commit 1c2a172 into master Apr 14, 2025
@Daimanta Daimanta deleted the jd/lighttpd-upgrade branch April 14, 2025 09:04
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.

4 participants