Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
prosdev merged 3 commits into from
Nov 8, 2025
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c66a426
feat(ci): enable automatic GitHub Releases
prosdev Nov 8, 2025
8010702
feat(experience-editor): prepare v1.1.0 release
prosdev Nov 8, 2025
c2f0623
maint: add Contributing section with changeset workflow
prosdev Nov 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .changeset/major-elephants-wash.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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

4 changes: 4 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down
59 changes: 59 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down Expand Up @@ -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`
Expand Down