Two repos are always marked "new" following an HA restart

rccoleman commented 3 years ago

Installation details

Description	Value
HACS version	1.8.0b0
Home Assistant version	0.118.1
Installation method for HA	Home Assistant OS KVM on Ubuntu

Checklist

[x] I'm running the newest version of HACS https://github.com/hacs/integration/releases/latest
[x] I have enabled debug logging for my installation.
[x] I have filled out the issue template to the best of my ability.
[x] I have read https://hacs.xyz/docs/issues
[x] This issue is related to the backend of HACS.
[x] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).

Describe the issue

Every time I restart Home Assistant, the "Xiaomi Mijia BLE MiBeacon monitor" integration and "Kiosk Mode" frontend repo show up as new repositories, even though I dismiss them each time. I'm running the 1.8.0b0 beta and can roll back HACS to see if it recurs, but I wanted to mention it while it's happening in case there's something I can debug.

I do note that the new field in hacs.repositories does indicate true for those repos, and switches to false when I dismiss them, but switches back to true every time I restart HA. I see this in the logs:

2020-11-20 11:06:20 DEBUG (MainThread) [custom_components.hacs] <Theme awolkers/home-assistant-themes> Running checks against master
2020-11-20 11:06:20 DEBUG (MainThread) [custom_components.hacs] <Plugin thomasloven/lovelace-card-mod> Running checks against 2.0.3
2020-11-20 11:06:20 DEBUG (MainThread) [custom_components.hacs] <Plugin gadgetchnnel/lovelace-card-preloader> Running checks against 0.0.5
2020-11-20 11:06:20 DEBUG (MainThread) [custom_components.hacs] <Integration twrecked/hass-aarlo> Running checks against v0.7.0-beta.7
2020-11-20 11:06:20 DEBUG (MainThread) [custom_components.hacs] <Integration briis/smartweather> Running checks against v2.0.4
2020-11-20 11:06:20 DEBUG (MainThread) [custom_components.hacs] <Plugin bramkragten/weather-card> Running checks against v1.5.0
2020-11-20 11:06:20 DEBUG (MainThread) [custom_components.hacs] <Theme KTibow/lovelace-dark-soft-ui-theme> Running checks against v0.59
2020-11-20 11:06:20 DEBUG (MainThread) [custom_components.hacs] <Integration custom-components/alexa_media_player> Running checks against v3.2.2
2020-11-20 11:06:20 DEBUG (MainThread) [custom_components.hacs] <Plugin custom-cards/upcoming-media-card> Running checks against 0.4.3
2020-11-20 11:06:20 DEBUG (MainThread) [custom_components.hacs] <Plugin maykar/kiosk-mode> All (0) checks passed
2020-11-20 11:06:20 INFO (MainThread) [custom_components.hacs] <Plugin maykar/kiosk-mode> Registration completed
2020-11-20 11:06:20 DEBUG (MainThread) [custom_components.hacs] <Integration custom-components/ble_monitor> All (0) checks passed
2020-11-20 11:06:20 INFO (MainThread) [custom_components.hacs] <Integration custom-components/ble_monitor> Registration completed
2020-11-20 11:06:25 DEBUG (MainThread) [custom_components.hacs] <Integration thomasloven/hass-browser_mod> Getting repository information
2020-11-20 11:06:25 DEBUG (MainThread) [custom_components.hacs] <Plugin kalkih/mini-graph-card> Getting repository information
2020-11-20 11:06:25 DEBUG (MainThread) [custom_components.hacs] <Integration custom-components/pyscript> Getting repository information

I'm including some others around the problematic repos to show that the ones that keep showing up as new say "All (0) checks passed", while the others say "Running checks against xxxx" and sometimes "Getting respository information".

Steps to reproduce

This repros for me each time I restart HA, started prior to the 1.8.0b0 update of HACS, and persists across HA updates (most recently, last night to 0.118.1).