mirror of
https://github.com/apricote/Listory.git
synced 2026-01-13 21:21:02 +00:00
b62dfa354b
# [1.17.0](https://github.com/apricote/Listory/compare/v1.16.4...v1.17.0) (2022-06-25) ### Bug Fixes * **api:** some listens pages are not full ([be38c38](be38c383ef)) * **frontend:** invalid react list keys ([fa2d1f4](fa2d1f426f)) * **frontend:** show empty report only when not loading ([79b375c](79b375ca08)) * **frontend:** use sensible default values for custom time selector ([4758338](4758338e99)) ### Features * **frontend:** nice login loading screen ([a443b3d](a443b3ddbc)) * **frontend:** use nice looking spinner ([01ed0c5](01ed0c5491)) * **frontend:** use transition for showing new data ([0c4de5d](0c4de5d56a))
21 lines
912 B
YAML
21 lines
912 B
YAML
apiVersion: v2
|
|
name: listory
|
|
description: Track your Spotify Listen History
|
|
|
|
# A chart can be either an 'application' or a 'library' chart.
|
|
#
|
|
# Application charts are a collection of templates that can be packaged into versioned archives
|
|
# to be deployed.
|
|
#
|
|
# Library charts provide useful utilities or functions for the chart developer. They're included as
|
|
# a dependency of application charts to inject those utilities and functions into the rendering
|
|
# pipeline. Library charts do not define any templates and therefore cannot be deployed.
|
|
type: application
|
|
|
|
# This is the chart version. This version number should be incremented each time you make changes
|
|
# to the chart and its templates, including the app version.
|
|
version: 1.17.0
|
|
|
|
# This is the version number of the application being deployed. This version number should be
|
|
# incremented each time you make changes to the application.
|
|
appVersion: 1.17.0
|