feat(ci): enable GitHub Releases and prepare v1.1.0 (#28)

## Overview
Enable automatic GitHub Release creation and prepare the first release
(v1.1.0) with changesets.

## Changes
- Add `createGithubReleases: true` to release workflow
- Add `fetch-depth: 0` for proper changelog generation
- Include changeset for v1.1.0 documenting features since v1.0.1
- Add Contributing section to README with changeset workflow
documentation

## What Happens After Merge
1. Release workflow detects the changeset
2. Automatically creates "Version Packages" PR
3. That PR will bump `@lytics/experience-editor` to v1.1.0
4. Merging the Version PR will publish to npm + create GitHub Release

## v1.1.0 Changelog
- Support for default field values to simplify form handling
- Content ranking options (affinity/popular) for recommendation widgets
- Date range display condition for time-based widget targeting
- Improved code quality with Biome linting and formatting

Author: prosdev

.changeset/major-elephants-wash.md

@@ -0,0 +1,12 @@
+---
+"@lytics/experience-editor": minor
+---
+
+Add field default values, content ranking, and date range display conditions
+
+- Support for default field values to simplify form handling and eliminate field-specific logic
+- Content ranking options (affinity/popular) for recommendation widgets
+- Date range display condition for time-based widget targeting
+- Improved code quality with Biome linting and formatting
+- Enhanced CI pipeline with automated quality checks
+

.github/workflows/release.yml

@@ -30,6 +30,9 @@ jobs:
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
+        with:
+          # Fetch all history for changesets to generate proper changelogs
+          fetch-depth: 0
 
       - name: Setup Node.js
         uses: actions/setup-node@v4
@@ -57,6 +60,7 @@ jobs:
           version: yarn version-packages
           commit: "chore: version packages"
           title: "chore: version packages"
+          createGithubReleases: true
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_CONFIG_PROVENANCE: true

README.md

@@ -11,6 +11,9 @@ Lytics Lab
   - [Configuration](#configuration)
     - [.env](#env)
     - [nx-cloud.env](#nx-cloudenv)
+  - [Contributing](#contributing)
+    - [Making Changes](#making-changes)
+    - [Documenting Changes](#documenting-changes)
   - [Iterating](#iterating)
     - [`yarn start`](#yarn-start)
     - [`yarn storybook`](#yarn-storybook)
@@ -61,6 +64,62 @@ To build, run tests, storybook, etc., you may be required to create a local `nx-
 NX_CLOUD_ACCESS_TOKEN={VALID_READ_WRITE_TOKEN}
 ```
 
+<hr>
+
+## Contributing
+
+We use [Changesets](https://github.com/changesets/changesets) for version management and automated releases. See [CONTRIBUTING.md](CONTRIBUTING.md) for detailed guidelines.
+
+### Making Changes
+
+1. Create a feature branch
+2. Make your changes
+3. Run quality checks locally:
+   ```sh
+   yarn lint
+   yarn typecheck
+   yarn test
+   yarn build
+   ```
+4. Create a changeset documenting your changes
+5. Open a pull request
+
+### Documenting Changes
+
+When you make user-facing changes, create a changeset:
+
+```sh
+yarn changeset
+```
+
+This will prompt you to:
+- Select which packages changed
+- Choose the version bump type (major/minor/patch)
+- Write a summary of your changes
+
+The changeset will be included in your PR and used to automatically generate changelogs and version bumps when merged.
+
+**Example workflow:**
+```sh
+# Make your changes
+git checkout -b feat/add-new-feature
+
+# Create a changeset
+yarn changeset
+# Select: @lytics/experience-editor
+# Type: minor (for new features)
+# Summary: "Add support for custom themes"
+
+# Commit everything
+git add .
+git commit -m "feat(experience-editor): add custom theme support"
+git push
+```
+
+For more details, see [CONTRIBUTING.md](CONTRIBUTING.md).
+
+<hr>
+
 ## Iterating
 
 ### `yarn start`