Skip to content

new branch - #1

Merged
magmacomputing merged 1 commit into
mainfrom
feature/rabbit
Oct 30, 2024
Merged

new branch#1
magmacomputing merged 1 commit into
mainfrom
feature/rabbit

Conversation

@magmacomputing

@magmacomputing magmacomputing commented Oct 30, 2024

Copy link
Copy Markdown
Owner

first pull request

Summary by CodeRabbit

  • New Features

    • Updated the version of the Tempo class to 0.2.0, ensuring users have access to the latest enhancements.
  • Bug Fixes

    • Resolved versioning discrepancies in the Default configuration object.

@coderabbitai

coderabbitai Bot commented Oct 30, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The changes in this pull request involve updating the version of the Tempo class from 0.1.0 to 0.2.0. This includes modifying the VERSION constant and updating the version property within the Default configuration object to reflect the new version number. No other alterations to the code structure, functionality, or logic have been made.

Changes

File Change Summary
lib/tempo.class.ts Updated VERSION constant from 0.1.0 to 0.2.0 and changed version property in Default object from 0.1.0 to 0.2.0.

Poem

In the meadow, hop and play,
A new version's here today!
Tempo's beat, now fresh and bright,
With 0.2.0, we take flight!
Hooray for changes, let’s all cheer,
A joyful tune for all to hear! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between df1370d and f6ecf96.

📒 Files selected for processing (1)
  • lib/tempo.class.ts (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • lib/tempo.class.ts

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@magmacomputing
magmacomputing merged commit 5e1acaa into main Oct 30, 2024
@magmacomputing
magmacomputing deleted the feature/rabbit branch October 30, 2024 21:02
magmacomputing added a commit that referenced this pull request Mar 24, 2026
magmacomputing added a commit that referenced this pull request Apr 28, 2026
magmacomputing added a commit that referenced this pull request Apr 30, 2026
* Add CI workflow for Tempo project

* Refactor CI workflow for Node.js setup and tests

* bump vitest

* working on ci.yml

* review 1st pass

* patch env in CI.yml

* debug in compact.time

* debug in tempo.class

* debug Intl.Locale

* test Intl.Local('en-us')

* mdy Fallback list

* clean-up timeZones fallback

* more debug fallback timeZones

* cut down on debug

* isMonthDay

* fix to $setEvents

* add bench/ for CI testing

* Options grouping, isMonthDay

* post-merge baseline

* rm spyOn from test-scripts

* Tempo.config

* test-cases passing

* doc/tempo.month-day

* test sbox

* draw a line... layout ordering

* new scripts in package.json

* PR review #1 updates

* PR review #2 updates

* PR review #3 updates

* #library

* resolve some final typings

* realign test-scripts

* plan

* PR review #4 updates
magmacomputing added a commit that referenced this pull request Jun 5, 2026
* Add CI workflow for Tempo project

* Refactor CI workflow for Node.js setup and tests

* bump vitest

* working on ci.yml

* review 1st pass

* patch env in CI.yml

* debug in compact.time

* debug in tempo.class

* debug Intl.Locale

* test Intl.Local('en-us')

* mdy Fallback list

* clean-up timeZones fallback

* more debug fallback timeZones

* cut down on debug

* isMonthDay

* fix to $setEvents

* add bench/ for CI testing

* Options grouping, isMonthDay

* post-merge baseline

* rm spyOn from test-scripts

* Tempo.config

* test-cases passing

* doc/tempo.month-day

* test sbox

* draw a line... layout ordering

* new scripts in package.json

* PR review #1 updates

* PR review #2 updates

* PR review #3 updates

* #library

* resolve some final typings

* realign test-scripts

* plan

* PR review #4 updates
magmacomputing added a commit that referenced this pull request Jun 10, 2026
magmacomputing added a commit that referenced this pull request Jun 11, 2026
* chore(release): bump version to 3.0.1 and prime CHANGELOG

* PR hotfix

* chore: require node >=22.0.0 in package.json files for json import support

* PR review #1

* test runs

* rollup #tempo/license

* PR 2nd review

* PR 4th review

* chore: update package-lock.json

* align package.json

* chore: regenerate package-lock.json to resolve vite conflicts

* add Typings to Standard Terms

* Term key naming convention
magmacomputing added a commit that referenced this pull request Jun 11, 2026
* chore(release): bump version to 3.0.1 and prime CHANGELOG

* PR hotfix

* chore: require node >=22.0.0 in package.json files for json import support

* PR review #1

* test runs

* rollup #tempo/license

* PR 2nd review

* PR 4th review

* chore: update package-lock.json

* align package.json

* chore: regenerate package-lock.json to resolve vite conflicts

* add Typings to Standard Terms

* Term key naming convention

* final Terms
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant