chore(timed): update timed-frontend image tag to v3.0.0-rc3

[derrabauke]

Description

Issues

Checklist

• This PR contains a description of the changes I'm making
• I updated the version in Chart.yaml
• I updated the changelog with an artifacthub.io/changes annotation in Chart.yaml, check the example in the documentation.
• I updated applicable README.md files using pre-commit run
• I documented any high-level concepts I'm introducing in docs/
• CI is currently green and this is ready for review
• I am ready to test changes after they are applied and released

[derrabauke]

@trowik you know what's wrong with that?

2023-01-24 10:29:44.204 GMT [176] ERROR: column "estimated_time" of relation "projects_project" already exists)?

[hairmare]

2023-01-24 10:29:44.204 GMT [176] ERROR: column "estimated_time" of relation "projects_project" already exists)?

might be related to this:

• don't run dbmigrate twice timed#128

i triggered a re-run to be sure it isn't racy

[derrabauke]

@hairmare Let's put the timed-frontend image on ghcr.io too. Any objections?

[hairmare]

@hairmare Let's put the timed-frontend image on ghcr.io too. Any objections?

not at all, i approved you gh actions PR

[hairmare]

@derrabauke looks like it didn't push a tagged image because the tag already existed, easiest way forward is probably to tag another release so gh actions can do it's thing

[derrabauke]

@derrabauke looks like it didn't push a tagged image because the tag already existed, easiest way forward is probably to tag another release so gh actions can do it's thing

Thanks again for helping me with this struggle. ;) Will push another tag.

[hairmare]

lgtm

(well, with one more rebase that can be done via the gui and shouldn't need re-approval)