Update freikin/dawarich Docker tag to v1 #44
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/freikin-dawarich-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.32.0→1.7.11Release Notes
Freika/dawarich (freikin/dawarich)
v1.7.11Compare Source
Added
/map/v2instantly: 30 days of Berlin + a Prague-weekend trip, ~80 visits with tags and places, and stats anchored to the current calendar month. "Remove demo data" wipes everything in one click while preserving anything you've confirmed, edited, or built on top of (visits, trips, places, tags adopted by user action stay).Changed
pointstable are dropped on upgrade; on large self-hosted instances this frees several GB of disk.Fixed
start_at/end_atfilter on the backend, so all visits inside the viewport were rendered regardless of the date filter. #2817POST /api/v1/visitsno longer links a new visit to a place owned by another user. Passing a foreignplace_idis ignored — the visit gets a place owned by the requester at the requested coordinates, and the response no longer echoes the other user's place id or coordinates.v1.7.10Compare Source
⚠️ Upgrade notes
Added
PATCH /areas/:idroute.Changed
selection=true&sw_lat=…&ne_lng=…(debounced 400 ms) so a wide date range no longer hauls every visit at once. Timeline day-selection still loads the full day regardless of zoom.Fixed
traveled · 0mrows from stationary keepalive clusters; commutes that absorb adjacent stationary points are correctly labeled by their moving mode (e.g.drove) rather thanstationary. Hit Settings → Recalculate to apply to existing data.v1.7.9Compare Source
⚠️ Upgrade notes
GET /api/v1/visits/:id/possible_placesandPOST /api/v1/visits/:id/select_placefor alternatives. Theplace_visitstable will be dropped in a follow-up release.bin/rails dawarich:backfill_place_namesbin/rails dawarich:cleanup_suggested_placesAdded
OIDC_PKCE_ENABLED=true(off by default). #2282POST /api/v1/visits/:id/select_place— assign a Photon candidate to a visit.Changed
GET /api/v1/visits/:id/possible_placesreturns live Photon suggestions; the assigned place comes first with itsid, others haveid: null.GET/POST /api/v1/places/nearbynow includeid,source, andgeodataper item (additive).Place#has_many :visitsis nowdependent: :nullify— deleting a Place no longer deletes its visits.Fixed
select_placevalidates lat/lon bounds (422 on out-of-range) and serializes concurrent calls via PG advisory lock to prevent duplicate Places.select_placededups by name + 50 m proximity instead ofgeodataJSONB, working regardless ofSTORE_GEODATA.JWT_SECRET_KEYis unset;/trial/upgradenow redirects home. #2682Places::DeleteIfOrphanJobinstead of inlineafter_commit.DataMigrations::BackfillPlacesUserIdJobcorrectly excludes just-assigned places from the orphan-delete pass.user_id:anduser_ids:to survive stale Sidekiq jobs. #2740RemoveUnusedIndexesmigration drops invalidpointsindexes left by failedREINDEX CONCURRENTLYbefore removing unused ones. #2124h3-jsretains its upstream Apache-2.0 license header.v1.7.8Compare Source
⚠️ Upgrade notes
ALLOW_EMAIL_PASSWORD_REGISTRATIONenv var no longer doubles as a login gate. Email/password sign-in is now controlled by the newALLOW_EMAIL_PASSWORD_LOGINenv var (defaults totrue). To preserve OIDC-only sign-in after upgrade, setALLOW_EMAIL_PASSWORD_LOGIN=false.places.user_idfrom owning visits and permanently deletes any place that has no linked visits. Multi-user instances and instances with orphan rows from prior bugs should runrake places:backfill_user_id_dry_runfirst to see assigned/deleted counts. Single-user self-hosted instances are unaffected. The follow-up release will add aNOT NULLconstraint, so any new places created between this release and the next must carry auser_id.points.tracker_idfrom each point'sraw_data(GoogledeviceTag, OwnTrackstid— both stored as-is) or itsimport_id(legacy-import-<id>, visible in points and tracks API responses for backfilled rows), then recalculates stats, tracks, and digests for every user with tracks predating the fix. The enqueue job is Sidekiq-retry-safe and re-checks its predicate on each retry, so a crashed/restarted Sidekiq resumes cleanly without re-processing finished users. New installs are unaffected.User.find(<id>).reset_failed_otp_attempts!, or by completing the password-reset flow (which also clears the lockout).Changed
Added
POST /api/v1/auth/otp_challenge) and the web sign-in flow. Backup codes still work during a lockout so users with one stored can recover immediately. A notification email is sent to the account owner when a lockout is triggered. #2575Fixed
ALLOW_EMAIL_PASSWORD_LOGIN=false. See the upgrade note above. #2495capturedAtfield with the canonical UTC instant (from Immich'sfileCreatedAt/ PhotoPrism'sTakenAt) alongside the existinglocalDateTimekey, which continues to return the source's wall-clock value. Map v2 usescapturedAtfor time display. #2253<trk>or<trkseg>elements no longer merges them into a single track when timestamps overlap or arrive out of order (e.g. Garmin daily-file exports); each track and segment becomes its own track. When a<trk>declares<src>, that value is SHA1-hashed and used as a stable device identity so consecutive imports of the same device stay on the same track stream; with only<name>, identity is scoped to the import filename to prevent unrelated devices from colliding. #1726deviceTag. #337tracksunique index now scopes bytracker_id(via aCOALESCE(tracker_id, '')expression so legacy NULL-tracker rows still can't duplicate), letting two devices produce a journey with the same start/end timestamps on one account without colliding on insert.v1.7.7Compare Source
⚠️ Breaking changes
Prometheus metrics backend migrated to Yabeda.
Dawarich now uses the Yabeda monitoring framework instead of
discourse/prometheus_exporter. Self-hosters who scrape Prometheus metrics from Dawarich should update their configuration.If Sidekiq is unreachable during a scrape, web returns its own metrics only and
logs a warning. Prometheus sees a momentary gap in
sidekiq_*rather than afailed scrape.
Scrape target (requires HTTP basic auth with
METRICS_USERNAME/METRICS_PASSWORD):http://dawarich_app:3000/metricsCustom
dawarich_archive_*metric names are unchanged. Dashboards and alerts built on these metrics continue to work.Infrastructure metric names have changed. If you have dashboards built on
ruby_*,active_record_*, or similar metrics emitted byprometheus_exporter, you must update them:ruby_http_requests_totalrails_requests_totalruby_http_request_duration_secondsrails_request_durationruby_sidekiq_jobs_totalsidekiq_jobs_executed_totalruby_sidekiq_failed_jobs_totalsidekiq_jobs_failed_totalruby_sidekiq_job_duration_secondssidekiq_job_runtime_secondsruby_sidekiq_queue_latency_secondssidekiq_queue_latencyruby_sidekiq_queue_backlog_totalsidekiq_jobs_waiting_countruby_sidekiq_process_countsidekiq_active_processesruby_puma_workerspuma_workersruby_puma_request_backlogpuma_backlogruby_puma_thread_pool_capacitypuma_pool_capacityactive_record_connection_pool_connectionsactiverecord_connection_pool_sizeruby_rss,ruby_heap_live_slots)Removed environment variables:
PROMETHEUS_EXPORTER_HOST,PROMETHEUS_EXPORTER_HOST_SIDEKIQ— no longer needed. Metrics are served in-process by each application.Retained environment variables:
PROMETHEUS_EXPORTER_ENABLED— still the single on/off switch.METRICS_USERNAME,METRICS_PASSWORD— unchanged.PROMETHEUS_EXPORTER_PORT— port the in-process Sidekiq metrics exporter binds to (default 9394).New optional environment variable:
SIDEKIQ_METRICS_URL— internal URL the web container uses to fetch Sidekiq metrics (defaulthttp://dawarich_sidekiq:9394/metrics). Override on Dokku, Kubernetes, or any deployment where the worker container's hostname differs from the docker-compose default.Prometheus scrape config example:
Fixed
Cache-Controlinstead. #1609v1.7.6Compare Source
Added
Fixed
America/Santiago). #2638http://even when the site was served over HTTPS via reverse proxy. #1469SMTP_AUTHENTICATION,SMTP_OPEN_TIMEOUT,SMTP_READ_TIMEOUT) are now env-configurable — Office 365 and similar no longer need a custom initializer. #1469safepasswordinstead ofpassword. #2636user_id,id, or timestamps.v1.7.5Compare Source
Added
Fixed
</>) now shift the time window by exactly one day, matching Map v1. Previously they shifted by the current window width, so a 00:00–23:59 selection paged back by 23h59m instead of 24h. #2548Changed
v1.7.4Compare Source
Fixed
JWT_SECRET_KEY. #2570safepassword. The old defaultpasswordprevented seeds from running due to the new 12-character minimum password length validation. Existing users were not affected. #2593v1.7.3Compare Source
Security
Fixes for several issues found in a static-analysis security audit. None of these have a known in-the-wild exploit, but operators should still upgrade.
POST /settings/users/import) — a malicious archive whose JSON manifest referenced files via..could attach arbitrary host files (e.g.config/master.key,/proc/self/environ) to the user's import record and download them.email_verifiedcheck or consent. The web flow now mirrors the mobile-API flow: the user must confirm the link.immich_url/photoprism_urlsettings missed RFC1918, CGNAT, IPv6 ULA, multicast and reserved ranges. Cloud installs now reject those; self-hosted gets a smaller blocklist that still catches non-http schemes, cloud-metadata IPs and multicast while permitting LAN / loopback / Docker DNS.POST /users/otp_challenge) had no rate limit, leaving 2FA brute-forceable given a leaked password. Added rack-attack throttles (5/15min per session, 20/15min per IP) plus an in-controller cap of 5 invalid attempts.family.namerendered throughnotification.content.html_safeis now passed throughsanitize.prometheus/prometheuscredentials for/metricsare gone — the endpoint refuses until bothMETRICS_USERNAMEandMETRICS_PASSWORDare set.params.permit!with the documented field whitelist.Added
locations.jsonand segment-array exports now import directly.Changed
0hand1hentries./settings/two_factornow asks for both your password and a current authenticator code (or one of your backup codes). The web form has been updated; API clients must sendpasswordANDotp_codetoDELETE /api/v1/users/me/two_factor./metricsendpoint: if you scrape Prometheus metrics, setMETRICS_USERNAMEandMETRICS_PASSWORDin your environment. With them unset,/metricsnow returns 503.0.0.0.0, multicast IPs, or the cloud-metadata169.254.169.254will be rejected. Standard LAN / Docker / loopback URLs continue to work.Fixed
location-history.jsonnow imports reliably. (#2437, #2587)No such file or directory @​ rb_sysopen - /tmp/.... #2446"Latitude","Longitude") are now recognized.db:migrate. #2576v1.7.2Compare Source
Removed
rails_pulseperformance monitoring has been removed entirely. The gem, its initializer (config/initializers/rails_pulse.rb), the/rails_pulseroute mount, the scheduledRailsPulse::SummaryJobandRailsPulse::CleanupJobcron entries, and allrails_pulse_*tables are gone. A new migrationDropRailsPulseTablescleans up existing installations on upgrade. This resolves a class of upgrade failures where therails_pulse_*tables ended up missing/half-applied on production. #2549Added
/api-docs.Fixed
500000 kminstead of500 km).bundle installcan locate theGemfile. Previously only sub-paths were mounted, leaving/var/app/Gemfilemissing. #1804latitude/longitudenull) no longer render as markers at Null Island (0°, 0°) — they are now correctly excluded from the photos layer. (#2464, #2465)v1.7.1Compare Source
Added
/map/v2instantly: 30 days of Berlin + a Prague-weekend trip, ~80 visits with tags and places, and stats anchored to the current calendar month. "Remove demo data" wipes everything in one click while preserving anything you've confirmed, edited, or built on top of (visits, trips, places, tags adopted by user action stay).Changed
pointstable are dropped on upgrade; on large self-hosted instances this frees several GB of disk.Fixed
start_at/end_atfilter on the backend, so all visits inside the viewport were rendered regardless of the date filter. #2817POST /api/v1/visitsno longer links a new visit to a place owned by another user. Passing a foreignplace_idis ignored — the visit gets a place owned by the requester at the requested coordinates, and the response no longer echoes the other user's place id or coordinates.v1.7.0Compare Source
The Timeline Release
The Timeline Feature in Map V2 is now a feature capable to fully replace Google Timeline's user experience and overshine it. Please enjoy responsibly.
Added
Changed
STORAGE_BACKEND=s3and provideAWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY,AWS_REGION, andAWS_BUCKET. For S3-compatible backends, additionally setAWS_ENDPOINT_URL(orAWS_ENDPOINT).<name>.zip.Fixed
config/schedule.yml, so no year-end emails went out. Yearly digests now fire on January 2nd at 06:00 UTC.countriestable has multiple rows sharing the same ISO code #2434.v1.6.1Compare Source
Added
Fixed
v1.6.0Compare Source
Added
Fixed
v1.5.1Compare Source
Fixed
v1.5.0Compare Source
Added
Changed
Fixed
counter_cache_columnerror in points counter reset job by using direct SQL count instead ofreset_counters.ON CONFLICTcardinality violations during reverse geocoding.TypeErrorcrash in transportation mode backfill when Google export files have unexpected JSON structure.beforedate filter being off by one day, excluding photos taken on the end date #747.maxattribute to all datetime-local fields #578.undefined method 'coordinates' for nilwhen trip path calculation hasn't completed yet #1356, #1765.beforedate filter being exclusive #1688./api/v1/health) triggering unnecessaryUser Loaddatabase queries on every request #1770.Invalid LatLng object: (NaN, NaN)when points have missing coordinates #1762.escape_javascriptproducing invalid JSON in the Stimulus data attribute.migrate_to_new_storagerake task crashing when export URL is blank, already migrated, or points to a directory instead of a file #1018, #1037.changeevent never fires with a single option #471.v1.4.0Compare Source
Added
Changed
Fixed
v1.3.4Compare Source
Added
Changed
settings.onboarding_completed) instead of relying solely on localStorage, preventing the modal from reappearing after browser data clears.Fixed
unwrapCoordinatesnow always returns a uniform array-of-arrays structure. #2038v1.3.3Compare Source
Added
Fixed
GET /api/v1/digests) now returns distance as a structured object withmeters,converted, andunitfields, matching the detail endpoint. Previously it returned raw meters, causing clients to display incorrect values. Breaking change: thedistancefield changed from an integer to an object. #2336save 60 10000rule caused a snapshot every ~60 seconds due to Sidekiq polling, generating tens of terabytes of disk writes over weeks. New defaults: snapshots every 15 minutes (10+ changes) or 5 minutes (100+ changes).v1.3.2Compare Source
Important: Self-hosters are not limited in any way. All features remain fully available regardless of plan. The new Lite plan and related limitations apply only to Dawarich Cloud users. If you're self-hosting, you can ignore the Lite plan details below. Self-hosted instances will continue to have access to all features without any restrictions.
Added
rack-attack. Lite: 200 requests/hour, Pro: 1,000 requests/hour. Self-hosted instances are exempt. Rate-limited responses return 429 withRetry-Afterheader.GET /api/v1/planendpoint returning the user's current plan and feature availability.X-Total-Points-In-RangeandX-Scoped-Pointsresponse headers on the points API, allowing clients to detect when data is being windowed.Changed
start_at,end_at) are now treated as Unix timestamps directly. Previously they were passed throughTime.zone.parse, which could return unexpected results. If you were relying on the old behavior for numeric strings, update your API calls accordingly.planin thesubscriptionobject.v1.3.1Compare Source
Changed
Fixed
v1.3.0Compare Source
The Storage & Timeline Interaction Release
This release adds a dedicated
motion_datacolumn for transportation-relevant fields alongside the existingraw_data. Users can now set their timezone for accurate date/time display across the app. The Timeline feed in Map v2 gains richer map interaction: hovering a journey highlights its track with an animated border, clicking zooms to fit and selects it, and expanding a day shows visit markers even when the Visits layer is off. User data export/import is enhanced with a new v2 format using JSONL files and monthly splitting for large datasets, while remaining backward-compatible with the old format.Added
TIME_ZONEenvironment variable for existing users.motion_dataJSONB column on thepointstable for storing transportation-relevant fields separately fromraw_data.DataMigrations::BackfillMotionDataJob) to backfillmotion_datafromraw_datafor existing points.ARCHIVE_ENCRYPTION_KEYto use a custom key; otherwise derives fromSECRET_KEY_BASE. Existing unencrypted archives (format version 1) are read transparently.data.json).original_pathserialized as WKT andtrack_segmentsembedded as a nested array, preserving transportation mode detection data across export/import cycles.sharing_uuidon import for security — old share links from the original user won't work for the importing user.Changed
motion_datacolumn alongsideraw_data, enabling efficient transportation mode detection.raw_data(full original payload) andmotion_data(transportation-relevant fields).STORE_GEODATAsetting now correctly controls whether geodata is written during reverse geocoding.idx_points_user_citydatabase index (304 MB) and replaced the fullreverse_geocoded_atindex (1,149 MB) with a smaller partial index covering only un-geocoded rows.RAILS_ENVindocker-compose.ymlis nowproductioninstead ofdevelopmentFixed
v1.2.0Compare Source
Changed
Added
GET /api/v1/insights) returning year overview with totals, activity heatmap, and streak data for the mobile app.GET /api/v1/insights/details) returning year-over-year comparison and travel patterns for the mobile app.GET/POST/DELETE /api/v1/digests) allowing the mobile app to list, view, generate, and delete yearly digests. Digest generation runs asynchronously via Sidekiq and returns202 Accepted. Digest detail supports conditional GET (Last-Modified/304 Not Modified).Fixed
v1.1.0Compare Source
The Timeline Release
In Map V2 Tools, user can now enable Timeline tool, which allows to quickly navigate through time and see how their location changed throughout the day. It can also be used to replay a trip by clicking the play button. Timeline tool always spans across 24 hours, but you can change the date by clicking on the date picker. Timeline tool is available only on Map V2.
Added
Fixed
.to_symfor nil in Sidekiq. #2190/api/v1/statsnow works faster.Changed
v1.0.4Compare Source
Fixed
v1.0.3Compare Source
Fixed
Added
SMTP_STARTTLSenvironment variable to enable STARTTLS for SMTP connections. Disabled by default.v1.0.2Compare Source
The Insights, Transportation Mode Detection and Supporter Verification release
Quiet a few big things in this release! It starterted with the idea of adding the Insights page. I experimented with it a bit to see what kinds charts and visualizations we can already have based on the existing data. There were some, but one of the most exciting to me would be the ability to see the Activity Breakdown: now many hours I spent walking, driving and running. Spoiler: I didn't run that much last year :) Anyway, to get that, we needed to have transportation mode detection for tracks. So naturally I went ahead and implemented that as well. Now, not only we can see the activity breakdown, but also, on the Map V2, if you click on a track (Tracks layer should enabled), you will see the transportation modes for it. That's what I wanted for Dawarich for a long time, and I'm happy it's finally here! In the map settings panel, there is now Transportation Mode Detection section, where you can configure speed thresholds for each mode. By default, they are set to reasonable values, but you can tweak them as you wish. Changing the thresholds will recalculate modes for all tracks in the background, which may take a while depending on how many tracks you have.
Another thing introduced in this release, is support verification. Almost 150 people have supported us financially on Ko-fi, Patreon and GitHub Sponsors, and if you're one of them, on the Settings page you can now enter your email and verify your support. Verified supporters will get a special (disableable) badge in the navbar as a token of our appreciation. Thank you so much for supporting Dawarich!
Anyway, enjoy the release and don't forget to report any bugs you may find!
Added
Fixed
Tracks::BoundaryResolverJobnow uses deterministic exponential backoff instead of random delays, and stops retrying after 5 attempts to avoid infinite rescheduling.Changed
v1.0.1Compare Source
Added
Fixed
raw_data['properties']['date']field.asset.readandasset.view. #1730ALLOW_EMAIL_PASSWORD_REGISTRATIONandOIDC_AUTO_REGISTERenv vars are now being respected correctly. #1972points_countcounter cache is now properly updated when creating points via OwnTracks, Overland, and generic Points API. This fixes visit suggestions not working for users using HomeAssistant or similar integrations. #2167Changed
Removed
v1.0.0Compare Source
The 1.0.0 release. Same as in 0.37.3, but with updated version number. We're aiming to provide more stable releases going forward.
All the issues that are currently open in Github will be addressed in the upcoming releases.
v0.37.3Compare Source
Fixed
Changed
v0.37.2Compare Source
Fixed
Added
v0.37.1Compare Source
Fixed
v0.37.0Compare Source
Added
Changed
Changed
Fixed
v0.36.4Compare Source
Fixed
v0.36.3Compare Source
Added
ARCHIVE_RAW_DATAenv var to true will enable monthly raw data archiving for all users. It will look for points older than 2 months withraw_datacolumn not empty and create a zip archive containing raw data files for each month. After successful archiving, raw data will be removed from the database to save space. Monthly archiving job is being run every day at 2:00 AM. Default env var value is false.Fixed
v0.36.2Compare Source
The Map v2 release
In this release we're introducing Map v2 based on MapLibre GL JS. It brings better performance, smoother interactions and more features in the future. User can select between Map v1 (Leaflet) and Map v2 (MapLibre GL JS) in the Settings -> Map Settings. New map features will be added to Map v2 only.
Added
Fixed
v0.36.1Compare Source
Fixed
v0.36.0Compare Source
OIDC and KML support release
So, you want to configure your OIDC provider. If not — skip to the actual changelog. You're going to need to provide at least 4 environment variables:
OIDC_CLIENT_ID,OIDC_CLIENT_SECRET,OIDC_ISSUER, andOIDC_REDIRECT_URI. Then, if you want to rename the provider from "OpenID Connect" to something else (e.g. "Authentik"), setOIDC_PROVIDER_NAMEvariable as well. If you want to disable email/password registration and allow only OIDC login, setALLOW_EMAIL_PASSWORD_REGISTRATIONtofalse. After just 7 brand new environment variables, you'll never have to deal with passwords in Dawarich again!Jokes aside, even though I'm not a fan of bloating the environment with too many variables, this is a nice addition and it will be reused in the cloud version of Dawarich as well. Thanks for waiting more than a year for this feature!
To configure your OIDC provider, set the following environment variables:
Added
docker-compose.ymlfile to use an alternative PostGIS image for ARM architecture.Fixed
Changed
v0.35.1Compare Source
Fixed
v0.35.0Compare Source
⚠️ Important ⚠️
The default
docker-compose.ymlfile has been updated to provide sensible defaults for self-hosted production environments. This should not break existing setups, but it's recommended to review yourdocker-compose.ymlfile and update it accordingly.You can now set
RAILS_ENVenvironment variable toproductionto run Dawarich in production mode.Added
Fixed
Changed
s3and provideAWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY,AWS_REGION,AWS_BUCKETandAWS_ENDPOINT_URLenvironment variables to configure it.docker-compose.ymlfile updated to provide sensible defaults for self-hosted production environment..env.examplefile added with default environment variables.v0.34.2Compare Source
Fixed
v0.34.1Compare Source
Fixed
Changed
Added
v0.34.0Compare Source
The Family release
In this release we're introducing family features that allow users to create family groups, invite members, and share location data. Family owners can manage members, control sharing settings, and ensure secure access to shared information. Location sharing is optional and can be enabled or disabled by each member individually. Users can join only one family at a time. Location sharing settings can be set to share location for 1, 6, 12, 24 hours or permanently. Family features are now available only for self-hosted instances and will be available in the cloud in the future. When "Family members" layer is enabled on the map, family member markers will be updated in real-time.
Added
Fixed
Changed
v0.33.1Compare Source
Changed
Fixed
GET /api/v1/statsendpoint now returns correct 0 instead of null if no points were tracked in the requested period.v0.33.0Compare Source
Fixed
GET /api/v1/pointswill now return correct latitude and longitude values. #1502<gpxtag will now be detected correctly. #1775Changed
Added
Configuration
📅 Schedule: (UTC)
🚦 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.
4dab76a95etoebda402552ebda402552to146bc28dc7146bc28dc7to06662032cb06662032cbto65ffe3e0d165ffe3e0d1toab3f9171cfab3f9171cfto9dda0ff2289dda0ff228to685cdfba00685cdfba00to4663b2fa144663b2fa14to42bfe3d2fd42bfe3d2fdto42cb25ae8fchore(deps): update freikin/dawarich docker tag to v1to Update freikin/dawarich Docker tag to v1d6a82abcdcto661cb783e2661cb783e2to09b286846409b2868464tofc157acc35fc157acc35to3186c546c03186c546c0to625b2727e7625b2727e7to708c162c62View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.