…2556)* fix: display active events, fix time not displaying for some events* test: passing events view tests* style: different icon* Update views.pyCo-authored-by: Ee Durbin <ewdurbin@gmail.com>---------Co-authored-by: Ee Durbin <ewdurbin@gmail.com>

Bumps [django-admin-interface](https://github.com/fabiocaccamo/django-admin-interface) from 0.24.2 to 0.28.9.- [Release notes](https://github.com/fabiocaccamo/django-admin-interface/releases)- [Changelog](https://github.com/fabiocaccamo/django-admin-interface/blob/main/CHANGELOG.md)- [Commits](fabiocaccamo/django-admin-interface@0.24.2...0.28.9)---updated-dependencies:- dependency-name: django-admin-interface  dependency-type: direct:production  update-type: version-update:semver-minor...Signed-off-by: dependabot[bot] <support@github.com>Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>Co-authored-by: Jacob Coffee <jacob@z7x.org>

Bumps [django-pipeline](https://github.com/jazzband/django-pipeline) from 3.0.0 to 3.1.0.- [Release notes](https://github.com/jazzband/django-pipeline/releases)- [Changelog](https://github.com/jazzband/django-pipeline/blob/master/HISTORY.rst)- [Commits](jazzband/django-pipeline@3.0.0...3.1.0)---updated-dependencies:- dependency-name: django-pipeline  dependency-type: direct:production  update-type: version-update:semver-minor...Signed-off-by: dependabot[bot] <support@github.com>Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [factory-boy](https://github.com/FactoryBoy/factory_boy) from 3.2.1 to 3.3.1.- [Changelog](https://github.com/FactoryBoy/factory_boy/blob/master/docs/changelog.rst)- [Commits](FactoryBoy/factory_boy@3.2.1...3.3.1)---updated-dependencies:- dependency-name: factory-boy  dependency-type: direct:development  update-type: version-update:semver-minor...Signed-off-by: dependabot[bot] <support@github.com>Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* fix(frontend): add help text to story formCloses#2364* chore: source migration* fix: use meta class overrides instead* feat: linkify

Bumps [python-decouple](https://github.com/henriquebastos/python-decouple) from 3.4 to 3.8.- [Release notes](https://github.com/henriquebastos/python-decouple/releases)- [Changelog](https://github.com/HBNetwork/python-decouple/blob/master/CHANGELOG.md)- [Commits](HBNetwork/python-decouple@v3.4...v3.8)---updated-dependencies:- dependency-name: python-decouple  dependency-type: direct:production  update-type: version-update:semver-minor...Signed-off-by: dependabot[bot] <support@github.com>Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>Co-authored-by: Jacob Coffee <jacob@z7x.org>

Bumps [django-tastypie](https://github.com/django-tastypie/django-tastypie) from 0.14.6 to 0.14.7.- [Release notes](https://github.com/django-tastypie/django-tastypie/releases)- [Commits](django-tastypie/django-tastypie@v0.14.6...v0.14.7)---updated-dependencies:- dependency-name: django-tastypie  dependency-type: direct:production  update-type: version-update:semver-patch...Signed-off-by: dependabot[bot] <support@github.com>Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [cssselect](https://github.com/scrapy/cssselect) from 1.1.0 to 1.2.0.- [Changelog](https://github.com/scrapy/cssselect/blob/master/CHANGES)- [Commits](scrapy/cssselect@v1.1.0...v1.2.0)---updated-dependencies:- dependency-name: cssselect  dependency-type: direct:production  update-type: version-update:semver-minor...Signed-off-by: dependabot[bot] <support@github.com>Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* chore: remove obsolete version entry from composeCurrently raises a warning:   the attribute `version` is obsolete, it will be ignored,   please remove it to avoid potential confusionSigned-off-by: Mike Fiedler <miketheman@gmail.com>* docs: staging site does not existSigned-off-by: Mike Fiedler <miketheman@gmail.com>* docs: format the link to be clickableSigned-off-by: Mike Fiedler <miketheman@gmail.com>* docs: use what's currently in docker-compose.ymlSigned-off-by: Mike Fiedler <miketheman@gmail.com>* docs: remove version specificitySigned-off-by: Mike Fiedler <miketheman@gmail.com>---------Signed-off-by: Mike Fiedler <miketheman@gmail.com>

…r end at a future year (#2500)* Add Methods To Check If Event Starts And Ends This Year* Set Up Templates For Querying Start And End YearsPassed variables to the time_tag template [time_tag.html] that checks if an event was scheduled to start or end with the current year.* Insert New Test Data And Update test_views.pyMore events are created to test particular scenarios of events especially events set to start or end at a future year.* Time Tag Now Shows Year For Events With Details Not Within The Current YearThe time tag now displays the year when an event will occur. This is only for events that have been scheduled to start or end in at a future year. The accompanying functional tests have also been included.* Move All Test Data To Functional TestAll test data concerning the provision of data to serve the functional tests have been moved to the functional test.As it improves readability.All other test data at test_views.py was resetto accommodate for the reduction in number of test data instances.* Functional Test For Displaying Year Of Event For Future Events Now Implemented With Unit Tests* Remove Functional Test For Displaying Year Of Future EventSince the current CI at the main branch does not support selenium [web driver] operations, the functional test which depends on selenium to run has been removed.* Handle Case When Call To Next Event Returns None* Fix Erroneous Addition To Dev RequirementsThis error was introduced in115af08* Refactor Tests For Relevant Year String Rendering At Events Page- Updated the test methods `test_scheduled_to_start_this_year_method` and `test_scheduled_to_end_this_year_method` to better reflect event scheduling edge cases.- Added assertions to verify when events are not scheduled to start or end within the current year.- Utilize `unittest.mock` to clamp down datetime-sensitive tests.---------Co-authored-by: Jacob Coffee <jacob@z7x.org>

* chore: avoid running Actions twice on PRRefs:https://github.com/orgs/community/discussions/57827#discussioncomment-6579237* chore: run once

* add a static container for handling local frontend dev* resulting css files

* Add a utility for purging Fastly by Surrogate-Key* add a postdeploy step to purge surroage-keys for static files

Instead of using a particular resolution on an object, which differsbetween `datetime.date` and `datetime.datetime` objects, operate onparent class of `datetime` and convert all `dt` to timezone-aware`datetime` values.This is also in accordance to the model field being a `DateTimeField`,so we should always be passing the correctly-created object, instead ofa `datetime.date()`, raising `received a naive datetime` warnings.Removes unused constants.Signed-off-by: Mike Fiedler <miketheman@gmail.com>Co-authored-by: Ee Durbin <ewdurbin@gmail.com>

Revert "Improve static deploy (#2609)"This reverts commit18e1d74.

* feat(infra): do not cache static 404s* feat(infra): apply condition