<commit_before># This file keeps track of the changes to the project.  We use it both to
# document the changes, and to find the most recent version numbers.  See the
# release process documented in docs/process.rst for details.

# This file uses the YAML format because it is easy to write and it is easy to
# convert to JSON, which seemed like a reasonable goal in case we want to use
# this data in the GUI itself at some point.  Here's an example of how to
# write the changes data.

# - unreleased:
# - 0.5.0:
#   - Did something
#   - Did something else
#   - >
#     Another thing that spans multiple lines
#     like this
# - 0.4.0:
#   - Something!
#   - Ooh!

# Release identifiers in this file should always be "unreleased" or
# [NUMBER].[NUMBER].[NUMBER] per http://semver.org/ .
#- unreleased:
- 1.2.3:
    - Update header to fix in new upcoming site theme.
    - Link to the MAAS web ui when the GUI detects it's in a MAAS environment.
    - Add deploy-target query parameter to auto deploy something via a link.
    - (FIX) Update to make sure bundle deployments occur with "options" set.
    - (FIX) Auto placed units not showing in the machine list.
    - (FIX) Update relations to work in a one to many endpoint scenario.
    - >
      Under the ":flags:/as" feature flag, work on the added service bar
      progresses. Track the list of deployed services and enable you to show
      and hide services and units in both service view and machine view.
- 1.2.2:
    - >
      New settings UI in the keyboard help.
      Use the keyboard shortcut key ? to view the settings and to adjust things
      like the name of the environment, force enable containers support in
      machine view, and disable the cookie banner.<commit_msg>Set version back to unreleased.<commit_after># This file keeps track of the changes to the project.  We use it both to
# document the changes, and to find the most recent version numbers.  See the
# release process documented in docs/process.rst for details.

# This file uses the YAML format because it is easy to write and it is easy to
# convert to JSON, which seemed like a reasonable goal in case we want to use
# this data in the GUI itself at some point.  Here's an example of how to
# write the changes data.

# - unreleased:
# - 0.5.0:
#   - Did something
#   - Did something else
#   - >
#     Another thing that spans multiple lines
#     like this
# - 0.4.0:
#   - Something!
#   - Ooh!

# Release identifiers in this file should always be "unreleased" or
# [NUMBER].[NUMBER].[NUMBER] per http://semver.org/ .
- unreleased:
- 1.2.3:
    - Update header to fix in new upcoming site theme.
    - Link to the MAAS web ui when the GUI detects it's in a MAAS environment.
    - Add deploy-target query parameter to auto deploy something via a link.
    - (FIX) Update to make sure bundle deployments occur with "options" set.
    - (FIX) Auto placed units not showing in the machine list.
    - (FIX) Update relations to work in a one to many endpoint scenario.
    - >
      Under the ":flags:/as" feature flag, work on the added service bar
      progresses. Track the list of deployed services and enable you to show
      and hide services and units in both service view and machine view.
- 1.2.2:
    - >
      New settings UI in the keyboard help.
      Use the keyboard shortcut key ? to view the settings and to adjust things
      like the name of the environment, force enable containers support in
      machine view, and disable the cookie banner.
{'fraction_non_alphanumeric': 0.06600284495021337, 'fraction_numerical': 0.0068278805120910386, 'mean_word_length': 2.8468271334792123, 'pattern_counts': {'":': 2, '<': 3, '<?xml version=': 0, '>': 9, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4685245', 'n_tokens_mistral': 972, 'n_tokens_neox': 931, 'n_words': 527}