How was the release and versioning process carried out?

Release and versioning in frontend development are usually based on semantic versioning (SemVer) — the MAJOR.MINOR.PATCH format.

• MAJOR — major changes that are incompatible with previous versions.
• MINOR — adding functionality without breaking backward compatibility.
• PATCH — bug fixes.

The release process goes through development, testing, and deployment stages. CI/CD is often used to automate build and deployment.

For version control of frontend resources, file hashing (content hashing) is used so browsers load updated versions instead of caching old ones.

Example of Webpack configuration for hashing:

output: {
  filename: '[name].[contenthash].js',
  path: path.resolve(__dirname, 'dist'),
},

This helps manage caching and makes it easier to roll back to previous versions if needed.