Skip to content

fix: Hashtag model now accepts 'text' field from API #21

fix: Hashtag model now accepts 'text' field from API

fix: Hashtag model now accepts 'text' field from API #21

Triggered via push December 28, 2025 22:41
Status Success
Total duration 26s
Artifacts

test.yml

on: push
Matrix: test
All tests passed
2s
All tests passed
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
Python 3.10
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>0ObJRaQAAAAA6r5fzH7RvTKKVVmmv6sA+UEhMMzBFREdFMDQxOABFZGdl
Python 3.10
Failed to restore: Cache service responded with 400
Python 3.11
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>0OrJRaQAAAAArAlGXxJ9JSokOQr7SrG6FUEFPRURHRTA1MTkARWRnZQ==
Python 3.11
Failed to restore: Cache service responded with 400
Python 3.12
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>0PbJRaQAAAAC4vHqiy0LTS5QJBhbF+Xc5UEhMMzBFREdFMDIxMQBFZGdl
Python 3.12
Failed to restore: Cache service responded with 400
Python 3.13
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>0O7JRaQAAAAAh/iePmuXKRLbOUxHmE4WbUEhYMzFFREdFMDUxOABFZGdl
Python 3.13
Failed to restore: Cache service responded with 400