Console tutorial date based badge

[wildemat]

Summary

• change description text of agent builder tutorial
• use 30 day time frame to apply the "new" badge given a tutorial's publish date (this really only is useful for the serverless release cadence)

[Copilot]

Pull request overview

This PR replaces hardcoded "new" badges with a date-based system that automatically determines if a tutorial should display the "New" badge based on a 30-day timeframe from its publication date.

Changes:

• Replaced the manual isNew boolean flag with a publishedAt Date field for tutorials
• Implemented an isNew() utility function that calculates if a tutorial is less than 30 days old
• Updated tutorial sorting to use orderBy by publication date instead of sortBy by the isNew flag

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

File	Description
console_tutorials_group.tsx	Replaced isNew boolean with publishedAt dates for each tutorial and updated sorting logic
utils.ts	Added isNew() function to determine badge visibility based on 30-day threshold
utils.test.ts	Added comprehensive test coverage for the isNew() function
jest.config.js	Added Jest configuration for the search_getting_started plugin

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: df9d2dd

Failed CI Steps

• Jest Tests #9
• Jest Tests #21
• FTR Configs #57
• Check API Contracts

Test Failures

• [job] [logs] Jest Tests #21 / FilterLabel should render properly
• [job] [logs] FTR Configs #57 / lens serverless - group 1 - subgroup 6 lens logsdb smoke testing functions support "after each" hook for "should visualize correctly ES|QL queries based on a LogsDB stream"
• [job] [logs] FTR Configs #57 / lens serverless - group 1 - subgroup 6 lens logsdb smoke testing functions support Scenarios with changing stream type Data-stream upgraded to LogsDB scenarios LogsDB stream with an additional TSDB stream downsampled should visualize correctly ES|QL queries based on a LogsDB stream
• [job] [logs] Jest Tests #9 / Mappings editor: core component props semantic_text field tests updates mapping with reference field value for semantic_text field

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
searchGettingStarted	264	265	+1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
searchGettingStarted	180.1KB	180.4KB	+251.0B

History

• 💔 Build #397025 failed 3783415
• 💔 Build #396993 failed 1e0f709
• 💔 Build #396246 failed 61f1c96

[kibanamachine]

Starting backport for target branches: 9.3

https://github.com/elastic/kibana/actions/runs/22150746053

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	9.3	Backport failed because of merge conflicts You might need to backport the following PRs to 9.3: - [Scout] Improve test target definition and tagging (#251436)

Manual backport

To create the backport manually run:

node scripts/backport --pr 253505

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 253505 locally
cc: @wildemat

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 253505 locally
cc: @wildemat