Skip to content

feat: Django 6.0

feat: Django 6.0 #129

Triggered via pull request March 1, 2026 11:55
@adinhodovicadinhodovic
synchronize #40
django-6-0
Status Success
Total duration 49s
Artifacts

ci-cd.yml

on: pull_request
Matrix: test
Release
0s
Release
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
lint
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0WCmkaQAAAABlxgloJ3JtSb/jCp+Hf4enUEhMMzBFREdFMDIyMABFZGdl
lint
Failed to restore: Cache service responded with 400
test (3.12, django52)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ZSmkaQAAAABN2mjpOWdwS6TigkVhGHw2Q0hHRURHRTE5MTYARWRnZQ==
test (3.12, django52)
Failed to restore: Cache service responded with 400
test (3.13, django52)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0aimkaQAAAABV9Epg8A42SosNxizxZnSxQ0hJMzBFREdFMDMxMwBFZGdl
test (3.13, django52)
Failed to restore: Cache service responded with 400
test (3.13, django60)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0aSmkaQAAAAANmyUDi0TERJQuMRWfvEZGUEFPRURHRTA1MTQARWRnZQ==
test (3.13, django60)
Failed to restore: Cache service responded with 400
test (3.12, django60)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0aymkaQAAAADJHe18Ei1bTZsZ+sP89RyaUEhYMzFFREdFMDIxMwBFZGdl
test (3.12, django60)
Failed to restore: Cache service responded with 400