v9.3.0

What's Changed

• Feat: add support for grb alerts by @camilledzt in #53

New Contributors

• @camilledzt made their first contribution in #53

Full Changelog: v9.2.0...v9.3.0

v9.2.0

What's Changed

• add new event_type: EarlyWarning and add tests accordingly by @FusRoman in #51

Full Changelog: v9.1.0...v9.2.0

v9.1.0

What's Changed

Bug Fixes

• Fix Slack interactive actions triggering unintended processes by @FusRoman in #49
  Previously, the /api/slack/actions endpoint would launch the automatic_gwemopt_process() workflow for any interactive button click, regardless of which button was pressed.
  This caused unwanted observation plan executions when other buttons were present in the Slack message.

  Changes:

  • Added filtering on action_id so that only the Run Observation Plan button triggers the workflow.
  • Other actions are now explicitly ignored and return a short acknowledgment message.

Tests

• Added a new test case to ensure that non-matching action_id values are ignored and do not trigger the process.

---

Upgrade Notes

No configuration changes are required.
To take advantage of the fix:

• Ensure that your Slack messages use a consistent action_id (e.g., run_obs_plan) for the "Run Observation Plan" button.
• Deploy this version so that the filtering is applied.

---

Impact

This fix prevents accidental execution of observation plan workflows when users click on unrelated buttons in Slack messages.

Full Changelog: v9.0.1...v9.1.0

v9.0.1

What's Changed

• update file for production by @FusRoman in #47

Full Changelog: v9.0.0...v9.0.1

v9.0.0

What's Changed

• Slack interactivity to handle observation plan manual trigger by @FusRoman in #42

Full Changelog: v8.3.0...v9.0.0

v8.3.0

What's Changed

• Fix a bug with the alert classification. If no classification was available in a json alert, the previous versions crashed when taking the maximum class for an alert. Now, the method return None et the slack message display "No classification available"
  • linked to Issue/44/class getter crash bug by @FusRoman in #45
• Add a new CLI argument to specify if the kafka queue should restart from the beginning. Previously, it was always the case and was annoying when redeploying the application as all previous alerts was rehandle by the system

Full Changelog: v8.2.0...v8.3.0

v8.2.0

Full Changelog: v8.1.0...v8.2.0

• Added Docker entrypoint script (entrypoint.sh) to automatically run Alembic migrations on container startup.

v8.1.0

Full Changelog: v8.0.0...v8.1.0

• Fix the GW alert condition, which decides when to send a Slack notification. Previously, it was is_significant, but it is not enough as the gw_alert test can be sent to the Kafka topic (alerts identifier starting with an M). Change conditions for is_real_observation, which checks for significance and tests if the alert identifier starts with an S (real observations).

v8.0.0

What's Changed

Release 8.0.0

Major Features

• PostgreSQL integration via SQLAlchemy and Alembic. Includes a new init_db helper and the GW_alert model for persisting alerts in the gw_alerts table.
• Slack notifications revamped. Initial alert messages are minimal, with detailed threaded follow‑ups tracked through the database.
• GCN stream now database‑aware, exposing SQLAlchemy engine/session accessors.
• Docker Compose split into production and test stacks, with environment variables centralized in .env.
• End‑to‑end tests updated with new e2e and faster e2e_light markers (documented in the README).

Enhancements

• Updated dependencies: added sqlalchemy, psycopg[binary], alembic, python-dotenv, and more.
• Pre‑commit configuration now enforces Black/Flake8/isort with an 88‑character line length.
• README expanded with database usage and Alembic workflow details.

Bug Fixes

• Hotfixes since 7.0.0 include Docker Compose adjustments, spam log removal, and gwemopt version updates.

Development & Testing

• New SQLite-based fixtures and database tests verify alert model logic.

Overall, this release introduces major architectural changes with database support, improved alert handling, a refined Docker setup, and updated tests.

Full Changelog: v7.0.4...v8.0.0

v7.0.4

Full Changelog: v7.0.3...v7.0.4

• Update gwemopt version -> shift Colibri position from OHP to San Pedro Martir