Crawl Foundry
Updates

Read Crawl Foundry's public release history in context

The changelog is the public history of what changed in Crawl Foundry and when. Each entry is dated and tagged, so you can see new features, improvements, fixes and breaking changes at a glance. For how a feature works today, the current guides take precedence.

After reading a release note, return to the current product guides for the steps that apply today.

Dated history

Valid entries are sorted newest first and displayed by localized month and year.

Public change type

Feature, Improvement, Fix, and Breaking tags frame the kind of customer-facing change.

Current guidance

The relevant documentation and live product contract take over after the historical announcement.

Find the latest product changes

Open the changelog on the Crawl Foundry website. The newest entries appear first. Each entry gives the date, type of change, affected feature and what you can do differently.

Tags describe the kind of public change

TagHow to read it
FeatureA customer-facing capability or usable surface was added.
ImprovementAn existing workflow, result, explanation, or reliability boundary changed.
FixA defect with customer-visible impact was corrected.
BreakingA change requires special attention because prior behavior or compatibility no longer holds.

Filter by the change you are looking for

Choose All to see the full archive, or Feature, Improvement or Fix to narrow the list. If the list is empty, switch to All or another filter.

Dates help you connect a change to the period when you noticed it. Open the current feature guide for setup instructions.

Read the archive in your language

Use the language selector on the website. If an entry is unavailable in your language, check the English archive.

Use the date to understand an older entry

  • An entry describes the feature at the time it was published.
  • Later entries may describe further changes to the same feature.
  • Check the current guide for today's setup, limits and permissions.

To verify what actually ran in your workspace, use the Activity log; a release announcement does not record your operations.

Move from the release note to current product guidance

1
Read the entry's date, tag, affected product area, and customer-facing outcome.
2
Open the relevant current documentation for setup, scope, permissions, limits, and troubleshooting.
3
Check the live product for the control or evidence described.
4
If behavior differs, preserve the current state and support code before escalating.

Check the current feature guide

When you follow an older release note, open the corresponding guide before changing your setup. It explains the controls and limits available today.

Example: Checking a change you noticed

A user notices a new control in Site Audit and filters the changelog to Feature entries to find when it was announced.

The entry explains the purpose; the current Site Audit guide explains setup, limits and troubleshooting as they work today.

Frequently asked questions

What do the changelog tags mean?

Feature marks a new capability, Improvement a changed workflow or result, Fix a corrected customer facing defect, and Breaking a change that can require action.

Why are some entries missing in my language?

English entries come from the main source; other languages show only entries that have been translated.

Is the changelog a complete record of changes?

No. It summarizes customer visible changes at publication time. It is not a commit log, incident history or billing record.