chore(deps): update internal dependencies (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
canonicalwebteam.discourse	==5.6.1 → ==7.1.1
canonicalwebteam.flask-base	==2.0.0 → ==3.1.1

---

Release Notes

canonical/canonicalwebteam.discourse (canonicalwebteam.discourse)

v7.1.1

Compare Source

Added

• Better error handling when api key and username is missing

v7.1.0

Compare Source

Updated EngagePages class

• Support optional value in get_engage_pages_tags to return tags for a specific engage page type
  Fixed DiscourseAPI filtering
• Only include keyword and value when both are provided; same for second_keyword/second_value to avoid sending None to the Data Explorer API

v7.0.0

Compare Source

Added Events class

• Created a new class to handle events from 'Discourse Calender (and events)' API
  Added EventsParser class
• Created a new parser to process the events retrieve by the Events class
  Updated check_for_category_updates & check_for_topic_updates
• Moved from Category into DiscourseAPI
  Updated Category class
• The function get_topics_in_category now returns an array of objects

v6.3.0

Compare Source

Updated EngagePages class

• Remove duplicated tags from the list of tags returned from get_engage_pages_tags

v6.2.0

Compare Source

Added _inject_custom_css def

• A function that finds css directives ([style=CLASSNAME]) in the soup and applies to them to the next found element.

v6.1.1

Compare Source

Updated EngagePages class

• Pass values for the provided keys, even if the values are empty or null, as they can be a filter themselves.

v6.1.0

Compare Source

Updated Category class

• Check for additions or deletions of topics within a category and update cached data if needed

v6.0.0

Compare Source

Updated Category class

• Removed to template handling from within the Category class.
• Bump to 6.0.0, as the previous update was a major

v5.8.1

Compare Source

Changes

feat: Add third filter for querying engage pages (#​206)

This release was made possible by the following contributors:

@​britneywwc

v5.8.0

Compare Source

Added Category class

• A generic class for processing discourse categories and the topics they contain

v5.7.4

Compare Source

Changes

feat: Update query to include second keyword and value (#​203)
removed config.ps5 (#​202)
Include h3 to table of contents (#​200)

This release was made possible by the following contributors:

@​britneywwc and @​samhotep

v5.7.3: : Read href from masked links in metadata

Compare Source

Changes

chore: Bump version to 5.7.3 (#​198)
Read href instead of string from masked links (#​197)

This release was made possible by the following contributors:

@​britneywwc

v5.7.2

Compare Source

Changes

Add sort by functionality to takeovers 'cooked' content (#​196)

This release was made possible by the following contributors:

@​carkod

v5.7.1

Compare Source

Changes

Add limit and offset to allow pagination for engage pages and takeovers (#​193)

This release was made possible by the following contributors:

@​carkod

canonical-web-and-design/canonicalwebteam.flask-base (canonicalwebteam.flask-base)

v3.1.1

Compare Source

Add missing init file to fix the bug of missing opentelemetry module.

v3.1.0

Compare Source

• Add prettified logs to Development mode.
• Add JSON structured logs to Production mode.
• The logging "extra" argument can be used to print JSON data out into the logs.
• Custom parameter "handler" of type logging.Handler can be passed to FlaskBase to personalize log output.
• Traces added to logs if tracing is enabled (through paas-charm).
• Custom parameter "untraced_routes" to mark routes for which tracing should not be enabled.

Upgrade notes

For the production mode to output JSON structured logs you don't need to do anything, as it comes out of the box.
Be aware that you can now pass parameters to the logging method with the "extra" argument and anything you pass
will appear in the structured JSON log.

For the development prettified logs there is one step to be done.
Update your gunicorn entrypoint to add --logger-class canonicalwebteam.flask_base.log_utils.GunicornDevLogger
if you are in DEBUG mode.

One can pass a custom logging.Handler to FlaskBase in order to personalize the output of the logs.
All the work of setting the handler in all the appropriate places is done by FlaskBase.

v3.0.0

Compare Source

• Update to use the latest version of Flask, Werkzeug, gunicorn and gevent.
• Completely remove talisker as a dependency.
• Add per route metrics that report the number of requests, response time, and error rate. (These metrics will be picked up automatically by a statsd-server if you are using the 12f app charm)

Upgrade notes

This version will require a few updates to remove talisker usage in your application. Namely:

• In your entrypoint script, replace talisker.gunicorn.gevent with gunicorn.
• Replace any instance of talisker.requests with requests.
• Remove TALISKER_REVISION_ID from Dockerfile.
• Remove any usage of talisker loggers.
• Remove any usage of app.extensions["sentry"] as Sentry support was provided by talisker and is no longer available. You can use the sentry-sdk package directly to integrate Sentry into your Flask application.

v2.6.1

Compare Source

Changes

add SENTRY_DSN env var (#​90)

This release was made possible by the following contributors:

@​usamabinnadeem-10

v2.6.0

Compare Source

Changes

Add flask secret key (#​87)

This release was made possible by the following contributors:

@​samhotep

v2.5.0

Compare Source

Changes

feat: added custom worker class (#​86)
chore: update PyPI publish action to use stable release version (#​85)

This release was made possible by the following contributors:

@​Dampolo03, @​goulinkh and @​samhotep

v2.4.0

Compare Source

Fix Werkzeug version limit to work with current Flask 2.3.3.

v2.3.0

Compare Source

Add response content compression using Gzip

v2.2.1

Compare Source

Revert 2.1.0 changes to compression of JS and CSS assets

v2.2.0

Compare Source

• Add support for Python 3.12
• Update dependencies: talisker, Werkzeug
• Remove unused direct dependencies that are used by talisker: gevent, jinja2, markupsafe, itsdangerous gevent, jinja2, markupsafe, itsdangerous

Upgrade notes

This version will require changes in the Dockerfile to use a virtual environment as this is mandatory for Python 3.12.

Here is an example of how to upgrade to 2.2.0: canonical/ubuntu.com@82f04d9

v2.1.0

Compare Source

Add compression of JS and CSS assets

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[webteam-app]

Demo

Jenkins

demos.haus

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.18%. Comparing base (42e48e5) to head (91458ac).
Report is 48 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #348   +/-   ##
=======================================
  Coverage   71.18%   71.18%           
=======================================
  Files           2        2           
  Lines          59       59           
=======================================
  Hits           42       42           
  Misses         17       17           

Flag	Coverage Δ
python	71.18% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.