Back to Sealos

CHANGELOG 5.0.1 Beta2

CHANGELOG/CHANGELOG-5.0.1-beta2.md

5.1.12.1 KB
Original Source

Welcome to the v5.0.1-beta2 release of Sealos!🎉🎉!

Changelog

New Features

  • ebe7f51afe023810fc4e3538f4f2e46007d43002: feat: launchpad support secret userDomains (#5119) (@zjy365)

Bug fixes

  • 2fd2f07892660ce4fa0ad0e167082fbeb372d579: fix: cronjob arm64 image (#5113) (@zijiren233)
  • d3ba17bc4925707a32ae999e88019aaf3af23800: fix: node tls reject unauthorized (#5116) (@zijiren233)
  • bc0b5f72006a173f9bcac0e287fd9893efe728af: fix: some ui adjust and bug fix (#5097) (@mlhiter)

Other work

  • 8c0c34592369874ce178c956af713dba3c17a9ea: devobx ignore extra ports. (#5112) (@lingdie)
  • 1243fd31e8f2f8828e35f1c47e6e6cd19155ae3e: fix desktop and costcenter configs (#5114) (@xudaotutou)
  • 22d9a138f9a3f4cd04a4eb927639fd008972adff: fix devbox phase generate. (#5120) (@lingdie)
  • b6053c1c2601fafa0752cdaac4501606bd020a20: fix get default property (#5108) (@bxy4543)
  • 7b025ae80d215cd1fe860ed08bc69dc132185be3: fix init user (#5104) (@bxy4543)
  • d21832075623248f831df5f04b7a8962c3c83fb6: fix scripts: init account jwt secret (#5117) (@bxy4543)
  • 3081c5dc1abf65d751de29b52b1febeb3dbbad9a: fix(account-service): fix concurrency issue and add real name info api (#5103) (@HUAHUAI23)
  • 7b0be9352fa422f1abca8f232cd8c864db548f7e: release: sealos v5.0.1 beta2 (#5110) (@lingdie)
  • 7a4b7b91fe63b3b4747fc99d2753c1b7a409fd39: sealos v5.0.1-beta2 (#5071) (@lingdie)
  • 54a3bc28684df2f8427c2ff1cc3969a0dd79c534: style(costcenter): recharge discount (#5111) (@xudaotutou)
  • b78691a56704884d1da0544a2779b8f42b45d3f1: sync resourcequota objectstorage/size status used (#5102) (@nowinkeyy)
  • c80c265fd6838bbf071cefcfa077a4e4d0274fa4: 🤖 add release changelog using rebot. (#5100) (@sealos-release-robot)

Full Changelog: https://github.com/labring/sealos/compare/v5.0.1-beta1...v5.0.1-beta2

See the CHANGELOG for more details.

Your patronage towards Sealos is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.