fix: More intuitive min_bound_range behavior #272

	name: CI

	on:
	pull_request:
	branches:
	- "*"
	push:
	branches:
	- "*"

	jobs:
	lint:
	runs-on: ubuntu-latest
	steps:
	- uses: actions/checkout@v4
	- name: Use Node.js 12.x
	uses: actions/setup-node@v4
	with:
	node-version: 12.x
	- name: Cache Node.js modules
	uses: actions/cache@v4
	with:
	path: ~/.npm # npm cache files are stored in `~/.npm` on Linux/macOS
	key: ${{ runner.OS }}-node-12.x-${{ hashFiles('**/package-lock.json') }}
	restore-keys: \|
	${{ runner.OS }}-node-12.x
	${{ runner.OS }}-
	- name: Install dependencies
	run: npm ci
	- name: Lint the code
	run: npm run lint --if-present
	build:
	runs-on: ubuntu-latest

	strategy:
	matrix:
	node-version: [10.x, 12.x]

	steps:
	- uses: actions/checkout@v4
	- name: Use Node.js ${{ matrix.node-version }}
	uses: actions/setup-node@v4
	with:
	node-version: ${{ matrix.node-version }}
	- name: Cache Node.js modules
	uses: actions/cache@v4
	with:
	path: ~/.npm # npm cache files are stored in `~/.npm` on Linux/macOS
	key: ${{ runner.OS }}-node-${{ matrix.node-version }}-${{ hashFiles('**/package-lock.json') }}
	restore-keys: \|
	${{ runner.OS }}-node-${{ matrix.node-version }}
	${{ runner.OS }}-
	- name: Install dependencies
	run: npm ci
	- name: Build the project
	run: npm run build --if-present
	- name: Archive distribution bundle
	uses: actions/upload-artifact@v4
	with:
	name: dist-node${{ matrix.node-version }}
	path: \|
	dist

Provide feedback