fix: date in meshery design

[Nayan-Kute21]

Description

This PR fixes #2448

Notes for Reviewers

Signed commits

• [x] Yes, I signed my commits.

[welcome[bot]]

Yay, your first pull request! :thumbsup: A contributor will be by to give feedback soon. In the meantime, please review the Newcomers' Guide and sure to join the community Slack. Be sure to double-check that you have signed your commits. Here are instructions for making signing an implicit activity while peforming a commit.

[netlify[bot]]

✅ Deploy Preview for mesheryio-preview ready!

Name	Link
🔨 Latest commit	ad5f7bf55f506a5c864acb5e45800211759afcc7
🔍 Latest deploy log	https://app.netlify.com/projects/mesheryio-preview/deploys/6946dff30fec7700086edd73
😎 Deploy Preview	https://deploy-preview-2452--mesheryio-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[gemini-code-assist[bot]]

Summary of Changes

Hello @Nayan-Kute21, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves an issue related to the handling and display of date information within Meshery designs when generating artifact-hub packages. The changes ensure that the creation timestamp is consistently formatted using the RFC3339 standard and correctly embedded as a dedicated 'date' field in the output YAML, addressing the reported bug.

Highlights

• Date Formatting: The CreatedAt timestamp for Meshery designs is now explicitly formatted to the RFC3339 standard before being used.
• Date Inclusion: A new date field has been added to the generated YAML output for Meshery designs, ensuring the creation date is properly recorded.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/add-catalog.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

[^1]: Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

[leecalcote]

Catalog designs were missing in the deployment preview. A resync with master will help restore them so that this change can be previewed.

[Nayan-Kute21]

strange locally it is showing the acctual creation date something is off in the deployment preview.

[kishore08-07]

@Nayan-Kute21 Thank you for your contribution! Let's discuss this during the website call today at 6:30 PM IST | 8 AM CT Add it as an agenda item to the meeting minutes, if you would :)

[saurabhraghuvanshii]

Hey @Nayan-Kute21 where did you find out issue can you share. I'm not able to locate. everything looks good to me