This repository has been archived by the owner on May 5, 2024. It is now read-only.
feat(docker-image): update ghcr.io/foxxmd/multi-scrobbler docker tag to v0.7.1 #3727
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.6.3
->0.7.1
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
FoxxMD/multi-scrobbler (ghcr.io/foxxmd/multi-scrobbler)
v0.7.1
Compare Source
What's New?
Apprise Notification
Support for notifying of scrobbles and errors via Apprise using an apprise-api server. See the docs for configuration.
Disable Web
The API and Dashboard can now be disabled. This can be useful for users who do not want a point of ingress in to MS on insecure networks.
Full Changelog
Documentation
Features
Miscellaneous Tasks
Refactor
v0.7.0
Compare Source
See the majority of changes in the RC1 release
New Since RC1
v0.6.5
Compare Source
What's New?
Upstream Recent
Prior to 0.5.0 MS let you see "recently played" directly returned from a Source's upstream API (for those that have it IE spotify, lastfm, listenbrainz...) This was useful for determining if the Source's API was "behind" what had actually been played -- for instance sometimes Spotify's "recently played" can be delayed by minutes/hours which could result in backlogging not returning what you "know" was played more recently.
This is entirely a convenience for the user, rather than new functionality for MS, but had been missing as a feature. This release returns this feature to the frontend.
UI Improvements for Source-of-Truth
For some sources (Lastfm, Listenbrainz) MS always uses the recently played data as the source-of-truth for scrobbling to your clients, rather than MS's "player". This is due to information returned for "now playing" for these sources being less accurate than recently played data. This has functionally not changed but this discrepancy is now more clearly presented to the user in the UI via a
?
tooltip icon.Google Cast Stability Improvements
I have rewritten parts of the third-party library providing google cast (chromecast) functionality to be more stable and less prone to crashing the entire MS application. Reconnecting events should now be more reliable as well.
Last.fm Timeout Fixes
An issue causing requests to Last.fm to hang forever has been fixed and will now cause the request to timeout in a reasonable amount of time instead of freeze up MS #134
Existing Scrobble checks for non-english characters
A bug causing scrobbles with non-english character-symbols to potentially not match existing scrobbles from client has been fixed. #121
Docker Image Alternatives
An alternative debian-based docker image is now provided for x86/x64 host architectures through a
*-debian
flavored tag. This image may be used as a workaround if you experience sporadic networking issues with the regular docker images. #126Full Changelog
Features
Bug Fixes
Documentation
Miscellaneous Tasks
v0.6.4
Compare Source
What's New?
Google Cast Source
Support for Google Cast devices as Sources. This is particularly exciting because music platforms that do not have an API for exposing user Now Playing info (Pandora, Tidal, MixCloud, Soundcloud) can now be monitored if you play them through a Google Cast device. Additionally, since the Cast platform exposes generic Now Playing information virtually any app that plays music through Casting can now be monitored by MS.
Application tooling restructure and frontend platform migration
This is no functional change for end-users. This is an internal/development refactor but brings with it many benefits:
The only visible changes are:
API_PORT
anymore -- usePORT
for both dev/prod now.Source init improvements
All sources have been refactored to have more granular init stages:
If any stage fails more descriptive errors are logged for the failure and the stage it failed at is also described, giving users more insight into why a source failed to start as well as improving debugging.
App Crash Logging
App-crashing errors should now be logged before the app crashes. The easiest way to capture these logs is to set file logging to
warn
log level so they are stored to file. In your file-basedconfig.json
`:Deprecations and Future Changes
Maloja
Spotify Credentials
A future release will include a migration from the current spotify api library to the official spotify web sdk. The information stored for Spotify credentials in releases prior to 0.6.4 is insufficient and will require reauthentication by the user if, for example, the user upgrades directly from 0.6.2 -> 0.6.5+.
0.6.4 will store all required credential information needed for future releases. Simply upgrade to this version and wait a few hours for Spotify credentials to be refreshed.
Full Changelog
Features
Bug Fixes
Documentation
Miscellaneous Tasks
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.