11.07.2023

[charleslavon]

What's Changed

🎉 New Features

• Add /relayer-demo route by @Patrick1904 in Add /relayer-demo route #796
• feat: Update terms and privacy by @shelegdmitriy in feat: Update terms and privacy #786
• feat: Prepare settings page for idOS integration by @shelegdmitriy in feat: Prepare settings page for idOS integration #728
• Added Ledger to wallet selector by @erditkurteshiSQA in Added Ledger to wallet selector #800

🐛 Fixes

• Fixed navigation menu auto-hide in mobile by @erditkurteshiSQA in Fixed navigation menu auto-hide in mobile #792

Enhancements 🌟

• Support auto generated changelogs by @charleslavon in Support auto generated changelogs #789
• NEAR Org Landing Pages (Part 2 of 2) by @calebjacob in NEAR Org Landing Pages (Part 2 of 2) #798

New Contributors

• @mpeterdev made their first contribution in Feat/tos #4
• @milenakrawczyk made their first contribution in New Editor UI & Publish draft version #2
• @Patrick1904 made their first contribution in feat: Add return icon to search input #7
• @jon-lewis made their first contribution in Fix: tutorials typo on mobile #20
• @ChaoticTempest made their first contribution in chore: Swap out alpha search bar with chaotictempest #34
• @thisisjoshford made their first contribution in add zendesk support widget #66
• @petarvujovic98 made their first contribution in feat: Add NEAR Horizon navigation/routing #79
• @gutsyphilip made their first contribution in Fast Auth POC #55
• @BenKurrek made their first contribution in [NEW] Trial Account Support #107
• @MaximusHaximus made their first contribution in Add relayer functionality to fastauth #162
• @hcho112 made their first contribution in ONB-67 Added logic to remember the page before login and redirect back on success #199
• @HarisSQA made their first contribution in Nightly wallet  #209
• @0xhsy made their first contribution in add welldone wallet #203
• @jakestutzman made their first contribution in Update next.config.js #252
• @roshaans made their first contribution in DATA-75 feat: Rudderstack Analytics #272
• @itegulov made their first contribution in chore: update mpc-recovery mainnet url #250
• @frolvanya made their first contribution in fix: withdraw text typo #302
• @evgenykuzyakov made their first contribution in chore: Add more chains to the chainlist #354
• @Ishatt made their first contribution in Create main.yml #512
• @gabehamilton made their first contribution in Move 'Ready for Development' items to next sprint #751
• @caesium55ds made their first contribution in [Snyk] Upgrade eslint-config-next from 13.3.4 to 13.5.3 #744
• @erditkurteshiSQA made their first contribution in Fixed navigation menu auto-hide in mobile #792

Full Changelog: https://github.com/near/near-discovery/commits/latest

---

This discussion was created from the release 11.07.2023.

[charleslavon]

@thisisjoshford I've created this release & discussion to get feedback on what type of naming convention would be fit releases for releases on the near-discovery and near-discovery-components repo. Since these repos are not APIs or services to be consumed, I don't think it's necessary, and would be overly cumbersome, to use semantic versioning here. Maybe a pattern of using MM.DD.YYYY as a release name would be sufficient for our needs. Perhaps I'm wrong?

What say ye?

[thisisjoshford]

Sounds good to me. As long as we're organizing the releases like this I'm onboard :) Only suggestion would be to follow YYYY-MM-DD format for better archival organization.