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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

trux-bot[bot]
Copy link
Contributor

@trux-bot trux-bot bot commented Jan 29, 2024

This PR contains the following updates:

Package Update Change
ghcr.io/foxxmd/multi-scrobbler minor 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
  • (No Category) Add config section and config example for disabling web server #​150
Features
  • (mpris) Less noisy error handling
  • (No Category) Implement option for disabling web server #​150
  • (No Category) Implement notifications via Apprise
Miscellaneous Tasks
  • (No Category) Remove some unused packages
  • (No Category) Update schema
  • (No Category) Bump version for release
Refactor
  • (logging) Reduce noise for polling interval logging
  • (logging) Balance debug/verbose level logging
  • (No Category) Reduce usage of ErrorWithCause
  • (No Category) Optimize imports
  • (No Category) Use updated logger to reduce log file path logic complexity
  • (No Category) Remove pony-cause dependency

v0.7.0

Compare Source

See the majority of changes in the RC1 release

New Since RC1

  • Updated flatpak appstream metadeta to conform with new guidelines
  • Fixed flatpak build manifest to work with new ESM module configuration

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. #​126

Full Changelog

Features
  • (chrome) Used improved library
  • (lastfm) Implement nowPlaying lfm api call
  • (source) Implement recent from API
  • (sources) Improve Source of Truth usage and presentation to user #​134
  • (No Category) Add debug logging for user api requests
  • (No Category) Improved logging for last.fm api network errors #​115
  • (No Category) Implement debian-based image #​126
Bug Fixes
  • (frontend) Fix scss division deprecation warnings
  • (lastfm) Patch lfm library to actually implement a request timeout #​134
  • (scrobbler) Fix erasing non-english characters #​121
  • (No Category) Add patch-package as postinstall script so packages actually get patched
Documentation
  • (No Category) Add workarounds for rollup issues and flatpak disclaimer
  • (No Category) Add debian docker image network workaround to docs #​126 #​134
Miscellaneous Tasks
  • (No Category) Remove some unused packages
  • (No Category) Ignore apple cert extensions
  • (No Category) Make container image build tags agnostic to default branch name
  • (No Category) Add matrix for building debian flavor tag

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:

  • Refactored project from cjs to esm (new module standard)
  • Moved away from dead frontend platform (CRA) to Vite
    • Removed dependency on webpack
    • Removed api proxy required by CRA
    • Simplified app entry -- Vite is served through express middleware instead of having nodemon spawn separate processes for front/backend
  • Refactored project to use tsx runtime wrapper -- no longer need to compile to js to run dev/prod
    • Side-effect of this is stack traces reported in prod now point to actual source files with correct lines numbers

The only visible changes are:

  • a slight increase in docker image size due to bundling typescript/source files
  • developers do not need to use API_PORT anymore -- use PORT for both dev/prod now.

Source init improvements

All sources have been refactored to have more granular init stages:

  • build data -- any data that needs to be parsed (URLs for mopidy), built, or verified (credentials) happens here
  • test connection -- if the source can be checked for reach-ability it is done here
  • test auth -- if the source requires auth it is tested here

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-based config.json`:

{
  "logging": {
    "level": "debug",
    "file": "warn"
  }
  // ...
}

Deprecations and Future Changes

Maloja
  • Support for Maloja versions below 3.0.0 is now deprecated
    • Likely no one is using these versions as they are almost 2 years old but MS still supports them with additional logic that could (should) be simplified
  • A warning is emitting if Maloja version is below 3.2.0 due to lack of support for scrobbling album information
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
  • (chrome) Improve mdns discovery for docker
  • (chrome) Implement user filtering media by type
  • (chrome) Allow manual device connections
  • (chrome) Refactor mdns discovery to run on source heartbeat as well as startup
  • (chrome) Catch buffering media
  • (deezer) Fix credentials check during build data stage
  • (maloja) Improve error handling
  • (spotify) Prepare for future spotify lib migration by writing completing credential data
  • (subsonic) Improve error/response parsing and report errors correctly on startup #​129
  • (No Category) Improve discovery for network exceptions in error causes
  • (No Category) Improve data init stage log wording
  • (No Category) Log when heartbeat tasks start
Bug Fixes
  • (No Category) Actually throw auth failure so initialization fails correctly
  • (No Category) Fix isReady logic
  • (No Category) Fix status indicator color based on status text
  • (No Category) Fix status text based on initialization OK values
  • (No Category) Fix return values for source init startup
  • (No Category) Fix when to check connection
  • (No Category) Fix where retries are checked
  • (No Category) Better handling of uncaught exceptions and rejections
Documentation
  • (No Category) Chromecast docs and schema
  • (No Category) Add local source reference to flatpak manifest
Miscellaneous Tasks
  • (chrome) Switch to scoped chromecast-client to fix flatpak source generation limitation
  • (maloja) Deprecate support for versions below 3.0.0

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@trux-bot trux-bot bot requested a review from truxnell as a code owner January 29, 2024 16:10
@trux-bot trux-bot bot changed the title fix(docker-image): update ghcr.io/foxxmd/multi-scrobbler docker tag to v0.6.4 fix(docker-image): update ghcr.io/foxxmd/multi-scrobbler docker tag to v0.6.5 Feb 5, 2024
@trux-bot trux-bot bot force-pushed the renovate/ghcr.io-foxxmd-multi-scrobbler-0.x branch from 7ebc321 to 7dc03aa Compare February 5, 2024 17:09
@trux-bot trux-bot bot force-pushed the renovate/ghcr.io-foxxmd-multi-scrobbler-0.x branch from 7dc03aa to a300654 Compare March 9, 2024 05:11
@trux-bot trux-bot bot changed the title fix(docker-image): update ghcr.io/foxxmd/multi-scrobbler docker tag to v0.6.5 feat(docker-image): update ghcr.io/foxxmd/multi-scrobbler docker tag to v0.7.0 Mar 26, 2024
@trux-bot trux-bot bot force-pushed the renovate/ghcr.io-foxxmd-multi-scrobbler-0.x branch from a300654 to ef034fd Compare March 26, 2024 14:11
…to v0.7.1

| datasource | package                        | from  | to    |
| ---------- | ------------------------------ | ----- | ----- |
| docker     | ghcr.io/foxxmd/multi-scrobbler | 0.6.3 | 0.7.1 |
@trux-bot trux-bot bot force-pushed the renovate/ghcr.io-foxxmd-multi-scrobbler-0.x branch from ef034fd to 192a2a3 Compare April 11, 2024 14:12
@trux-bot trux-bot bot changed the title feat(docker-image): update ghcr.io/foxxmd/multi-scrobbler docker tag to v0.7.0 feat(docker-image): update ghcr.io/foxxmd/multi-scrobbler docker tag to v0.7.1 Apr 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants