{"id":"6865b6073e9810029216f300","title":"2025 05 25","path":"how-to/committee/release-notes/2025-05-25","contentMarkdown":"# 15th - 25th May - 2025 — Various changes\n## [build 152](https://github.com/nbarrett/ngx-ramblers/actions/runs/15009344257)\n### 2025-05-15 \n- Fixed image source on send notification\n### 2025-05-17\n - Provide better real-time feedback during walks upload: \n- This change was inspired by response to Serenity JS conversation [Alternative implementation of the ConsoleReporter #2797](https://github.com/orgs/serenity-js/discussions/2797#discussioncomment-13148635) \n- StageCrewMember DomainEventPublisher created to publish a DomainEventDataWithFinished via websocket when a InteractionFinished, TaskFinished, TestSuiteFinished, SceneParametersDetected event is notified \n- Bumped tsconfig script compiler target to be es2021 or later as serenity-js code now brought into compile scope as part of this change\n- Refinements to the upload audits and timing - Fixed a few imports to be ESM\n### 2025-06-14 \n - Migration of Walk and SocialEvent to ExtendedGroupEvent \n - Simplifies event management where local and Ramblers data need to be managed in conjunction with each other. The internal NGX-Ramblers data model for walks and social events is now standardised to follow the schema for Ramblers Walks and Events API, with any additional fields stored in ExtendedFields schema. \n - Due to increased validation in times and date input, timepickers have now been added to walk and social event edits. End time rounded to nearest 15 mins \n- Distance can now be entered in miles or km \n- Ascent can now be entered in feet or metres\n### 2025-06-19 to 21\n- Fixes to social event notification send and event creation and Fix to ramblers event matching to ensure links updated\n### 2025-06-24 \n###### Completed [#10 SEO-friendly walk links](https://github.com/nbarrett/ngx-ramblers/issues/10) and [#9 Update page title for walk view](https://github.com/nbarrett/ngx-ramblers/pull/9) \n- SEO-friendly slug (e.g. kebab-case conversion of event title) is now used as primary mechanism for querying and rendering single events. \n- Walk and social event routing changed initially perform page content lookup for the slug and then fallback to event lookup using url. \n- All website and email links now use seo-friendly links \n- Legacy ids (Ramblers or Mongo) still work for backward compatibility purposes. \n- If an event cannot be found for a slug, an event not found alert is displayed as per dynamic content lookup failure. \n- For sites that have Walk Population/Social Event Population as Walks Manager, query performance is temporarily reduced as there is no Ramblers provided API available for querying by slug (as per their own website). As a workaround, the NGX-Ramblers server has to do a full historic lookup of all events and match by slug. Performance will be resolved once https://github.com/nbarrett/ngx-ramblers/issues/34 has been implemented \n- For sites that have Walk Population/Social Event Population as Local, the url will be the date up until publishing to Ramblers occurs, then the ramblers url is used.\n- Fix server-side lodash imports \n- Turned off EventDispatchService logging\n- Set contact subject by optional query parameter\n###### Completed [#36 Enhance deployment workflows](https://github.com/nbarrett/ngx-ramblers/issues/36) \n- allow each environment to be a different stage \n- permit retry from a failed stage \n- only push latest docker tag to the registry if the branch is main \n- Log in to Docker Hub using docker/login-action@v3docker login \n- Support a run-time parameter for the build number but default to latest\n#### Screenshot is below with [link to actual deployment](https://github.com/nbarrett/ngx-ramblers/actions/runs/18925582625):\n\n\n\n\n### 2025-06-25 \n - further changes to read configs from configs.json when all is selected \n - added readme documentation for deploy-to-environments.yml","contentHtml":"15th - 25th May - 2025 — Various changes
\n\n2025-05-15
\n\n- Fixed image source on send notification
\n
\n2025-05-17
\n\n- Provide better real-time feedback during walks upload:
\n- This change was inspired by response to Serenity JS conversation Alternative implementation of the ConsoleReporter #2797
\n- StageCrewMember DomainEventPublisher created to publish a DomainEventDataWithFinished via websocket when a InteractionFinished, TaskFinished, TestSuiteFinished, SceneParametersDetected event is notified
\n- Bumped tsconfig script compiler target to be es2021 or later as serenity-js code now brought into compile scope as part of this change
\n- Refinements to the upload audits and timing - Fixed a few imports to be ESM
\n
\n2025-06-14
\n\n- Migration of Walk and SocialEvent to ExtendedGroupEvent
\n- Simplifies event management where local and Ramblers data need to be managed in conjunction with each other. The internal NGX-Ramblers data model for walks and social events is now standardised to follow the schema for Ramblers Walks and Events API, with any additional fields stored in ExtendedFields schema.
\n- Due to increased validation in times and date input, timepickers have now been added to walk and social event edits. End time rounded to nearest 15 mins
\n- Distance can now be entered in miles or km
\n- Ascent can now be entered in feet or metres
\n
\n2025-06-19 to 21
\n\n- Fixes to social event notification send and event creation and Fix to ramblers event matching to ensure links updated
\n
\n2025-06-24
\n\n\n- SEO-friendly slug (e.g. kebab-case conversion of event title) is now used as primary mechanism for querying and rendering single events.
\n- Walk and social event routing changed initially perform page content lookup for the slug and then fallback to event lookup using url.
\n- All website and email links now use seo-friendly links
\n- Legacy ids (Ramblers or Mongo) still work for backward compatibility purposes.
\n- If an event cannot be found for a slug, an event not found alert is displayed as per dynamic content lookup failure.
\n- For sites that have Walk Population/Social Event Population as Walks Manager, query performance is temporarily reduced as there is no Ramblers provided API available for querying by slug (as per their own website). As a workaround, the NGX-Ramblers server has to do a full historic lookup of all events and match by slug. Performance will be resolved once https://github.com/nbarrett/ngx-ramblers/issues/34 has been implemented
\n- For sites that have Walk Population/Social Event Population as Local, the url will be the date up until publishing to Ramblers occurs, then the ramblers url is used.
\n- Fix server-side lodash imports
\n- Turned off EventDispatchService logging
\n- Set contact subject by optional query parameter
\n
\n\n\n- allow each environment to be a different stage
\n- permit retry from a failed stage
\n- only push latest docker tag to the registry if the branch is main
\n- Log in to Docker Hub using docker/login-action@v3docker login
\n- Support a run-time parameter for the build number but default to latest
\n
\n\n![\"\"](\"https://ngx-ramblers.org.uk/api/aws/s3/site-content/a5d9cfba-3acd-4ffb-96cf-21f1068aa3dc.jpeg\")
\n2025-06-25
\n\n- further changes to read configs from configs.json when all is selected
\n- added readme documentation for deploy-to-environments.yml
\n
\n"}