Releases: balena-io/balena-mdns-publisher
Releases · balena-io/balena-mdns-publisher
v1.28.2
v1.28.1
v1.28.0
v1.27.201
v1.27.200
Update balena/open-balena-base Docker tag to v18.0.41
Notable changes
- Update Node.js to v22.18.0 [balena-renovate[bot]]
balena-io-modules/open-balena-base (balena/open-balena-base)
v18.0.41
(2025-07-31)
- Update Node.js to v22.18.0 [balena-renovate[bot]]
v18.0.41
(2025-07-31)
- Update Node.js to v22.18.0 [balena-renovate[bot]]
List of commits
1fb6b52 (Update balena/open-balena-base Docker tag to v18.0.41, 2025-07-31)
v1.27.199
Update balena/open-balena-base Docker tag to v18.0.40
Notable changes
- Update dependency npm to v11.5.2 [balena-renovate[bot]]
balena-io-modules/open-balena-base (balena/open-balena-base)
v18.0.40
(2025-07-30)
- Update dependency npm to v11.5.2 [balena-renovate[bot]]
v18.0.40
(2025-07-30)
- Update dependency npm to v11.5.2 [balena-renovate[bot]]
List of commits
d28cffb (Update balena/open-balena-base Docker tag to v18.0.40, 2025-07-30)
v1.27.198
v1.27.197
Update balena/open-balena-base Docker tag to v18.0.39
Notable changes
- patch: Remove obsolete/deprecated hosts [Anton Belodedenko]
balena-io-modules/open-balena-base (balena/open-balena-base)
v18.0.39
(2025-07-29)
- patch: Remove obsolete/deprecated hosts [Anton Belodedenko]
v18.0.39
(2025-07-29)
- patch: Remove obsolete/deprecated hosts [Anton Belodedenko]
List of commits
488300f (Update balena/open-balena-base Docker tag to v18.0.39, 2025-07-29)
v1.27.196
v1.27.195
Update dependency lint-staged to v16
Notable changes
- #1570
a7c0c88Thanks @ItsNickBarry! - When using--diff-filterwith theDoption to include deleted staged files, lint-staged no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error fromgit addlikefatal: pathspec 'deleted-file' did not match any files. 38f942eThanks @iiroj! - Removed an extraneous log entry that printedshouldHidePArtiallyStagedFilesto console output.- #1565
3686977Thanks @iiroj! - Lint-staged now explicitly warns about potential data loss when using--no-stash. - #1571
02299a9Thanks @iiroj! - Function tasks (introduced in v16.0.0) only receive the staged files matching the configured glob, instead of all staged files. - #1563
bc61c74Thanks @iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the--no-stashoption. This happened because--no-stashimplied--no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case. - #1536
e729daaThanks @iiroj! - A new flag--no-reverthas been introduced for when task modifications should be applied to the index before aborting the commit in case of errors. By default, lint-staged will clear all task modifications and revert to the original state. - #1550
b27fa3fThanks @iiroj! - Lint-staged now ignores symlinks and leaves them out from the list of staged files. - #1558
c37dc38Thanks @iiroj! - The minimum required Node.js version is lowered to20.17following [email protected]. - #1546
158d15cThanks @iiroj! - Processes are spawned using nano-spawn instead of execa. If you are using Node.js scripts as tasks, you might need to explicitly run them withnode, especially when using Windows: - #1546
158d15cThanks @iiroj! - The--shellflag has been removed and lint-staged no longer supports evaluating commands directly via a shell. To migrate existing commands, you can create a shell script and invoke it instead. Lint-staged will pass matched staged files as a list of arguments, accessible via"$@​": - #1544
5561321Thanks @YimingIsCOLD! - Correctly handle colon (:) characters in staged filenames. - #1533
5d53534Thanks @iiroj! - Improve listing of staged files so that lint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like: - #1526
630af5fThanks @iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier. - #1512
cbfed1dThanks @tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693. - #1509
8827ebfThanks @iiroj! - Change lint-staged's dependencies to use caret (^) ranges instead of tilde (~). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level. - #1504
1c7a45eThanks @iiroj! - Default TypeScript config filenames match JS equivalents. - #1504
9cc18c9Thanks @iiroj! - Add missing conditional exports syntax for TypeScript types. - #1500
a8ec1ddThanks @iiroj! - Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files: - #1501
9b79364Thanks @iiroj! - Handle possible failures when logging user shell for debug info. - #1495
e69da9eThanks @iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues. - #1493
fa0fe98Thanks @iiroj! - Added more help messages around the automaticgit stashthat lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing. - #1484
bcfe309Thanks @wormsik! - Escape paths containing spaces when using the "shell" option. - #1487
7dd8caaThanks @iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.